Bluetooth Assigned Numbers Explorer
Search Bluetooth Company Identifiers, advertising data types, Appearance values, adopted services, and member UUIDs across distinct assigned-number namespaces.
Apply assigned values with SimpleBLE
Decode advertisements, identify services, and inspect GATT data through one consistent cross-platform API.
Interpret values within their namespace
Bluetooth Assigned Numbers are divided into independent namespaces. The value 0x004C, for example, identifies Apple in the Company Identifier table but can represent a different assignment in another table. A numeric match is meaningful only when the field or protocol element that carries it is known.
The explorer therefore preserves the namespace on every result. When a value produces several matches, use the packet field, GATT attribute, or API property from which it came to select the correct interpretation.
Identify Manufacturer Specific Data
A Bluetooth Company Identifier is assigned to a member organization. In Bluetooth Low Energy advertising, it commonly appears as the first two octets of Manufacturer Specific Data, encoded least-significant octet first on air. The identifier names the assignee; it does not guarantee that the assignee manufactured the complete product.
Company Identifiers are not IEEE OUIs and are not derived from a device address. Use the Bluetooth Address & OUI Lookup when the source value is a public Bluetooth device address.
Decode AD types and appearance values
An Advertising Data Type identifies the meaning of an advertising or scan-response field. Common examples include Flags 0x01, Complete Local Name 0x09, Appearance 0x19, and Manufacturer Specific Data 0xFF.
The Appearance value is a separate 16-bit field that describes a generic device category and, where assigned, a subcategory. It is descriptive metadata rather than proof of a device model or its supported GATT services.
Distinguish adopted and member UUIDs
Adopted Service UUIDs identify services standardized by the Bluetooth SIG, such as Battery Service 0x180F and Heart Rate Service0x180D. Their 16-bit values can be expanded with the Bluetooth Base UUID when an API expects a 128-bit UUID.
Member UUIDs are 16-bit assignments allocated to Bluetooth SIG members. The organization name identifies the assignment holder, but the service meaning and payload format still come from that organization’s protocol documentation.
Reference the current Bluetooth SIG registry
The Bluetooth SIG maintains the authoritative Assigned Numbers document and downloads. The structured source tables are published in the Assigned Numbers repository. Assigned values can be added or renamed, so confirm release-sensitive decisions against the current registry.