Wiegand bit formats: 19 documented layouts across six widths

A bit count does not identify a layout. These 19 formats share six widths; three split their fields differently, so one number per width is a guess.

FormatBitsField splitParityConfidenceOn this site
HID H10301268 facility + 16 cardeven 2–13 / odd 14–25high✅
HID H10306 / Honeywell N100023416 facility + 16 cardeven 2–17 / odd 18–33high✅
AWID RS2 34-bit348 site + 24 card + 2 unassignednot publishedhigh—
Indala 34-bit Optus3411 site + 16 card + 7 unassignednot publishedlow—
Cardkey Smartpass 34-bit3413 site + 3 issue level + 16 card + 2 unassignednot publishedlow—
BQT 34-bit348 facility + 24 cardeven 2–17 / odd 18–33low—
Keyscan C150013610 OEM + 8 facility + 16 cardeven 2–18 / odd 19–35medium✅
Simplex S1290636not publishednot publishedlow—
AWID 36-bit36not publishednot publishedlow—
HID H103023735 cardeven 2–18 / odd 19–36 (boundary disputed)high—
HID H103043716 facility + 19 cardeven 2–18 / odd 19–36 (boundary disputed)high—
HID generic 37-bit3732 card + 3 unassignedeven 1–2 / odd 37–37medium—
PointGuard MDI 37-bit374 site + 29 card + 4 unassignednot publishedmedium—
ATS 32-bit3213 site + 17 card2 bits, positions not publishedmedium—
Generic WIE323212 site + 16 card + 4 unassignednonemedium—
Kantech K32328 site + 16 card + 8 unassignednot publishedmedium—
Nedap 32-bit3216 site + 16 cardnonemedium—
Maxxess 32-bit3214 site + 16 badge + 2 unassignednot publishedmedium—
HID Corporate 10003512 company + 20 card3 bits, interleavedmedium—

The width is not the format

Thirty-four bits is the clearest example. HID H10306 and Honeywell N10002 both use 16 bits of facility code and 16 bits of card number. AWID RS2 spends the same 34 bits as 8 bits of site code and 24 bits of card number; BQT keeps the facility code at 8 bits but gives the card number 24; Indala Optus publishes 11 bits of site code and leaves seven columns unmarked; Cardkey Smartpass splits the frame three ways — 13 bits of site code, 3 bits of issue level, 16 bits of card number. Feed an RS2 card to a decoder that assumes H10306 and it hands back a facility code and a card number that pass every internal check and open nothing.

Thirty-seven bits repeats the pattern inside one vendor: H10302 has no facility code at all — 35 bits of card number — while H10304 splits the same length into 16 bits of facility code and 19 bits of card number. A frame on its own cannot tell you which of the two it is.

Thirty-six bits is worse than ambiguous, because part of it is undocumented. Keyscan C15001 carries a 10-bit OEM code, 8 bits of facility code and 16 bits of card number; Simplex S12906 and AWID 36-bit are different layouts at the same length, and AWID uses its own modulation, so a standard HID-style reader cannot read those cards at all.

What this site does with 32, 35 and 37 bit

32 bit has at least five layouts — ATS, generic WIE32, Kantech K32, Nedap, Maxxess — and several carry no parity bits whatsoever, so a corrupted frame cannot be detected and any decoder output is unfalsifiable. Nedap is 16 + 16 with no parity: the same split as H10306 at half the length, which is exactly the trap this table exists to document.

35 bit is HID Corporate 1000: proprietary, with three parity bits interleaved through the data rather than sitting at the ends. Nothing public says where the interleaving starts and stops, so an implementation would be guessing on every frame.

37 bit is listed for both layouts and the tool does read them, but it will not build one. H10302 is 35 bits of card number with no facility code; H10304 splits the same length into 16 bits of facility code and 19 bits of card number. The blocker is the parity boundary: Nedap and promptzero/pacs make the two 18-bit regions overlap at bit 18, while Suprema starts the odd region at 18, and 35 data bits cannot be split evenly. So a 37-bit frame decodes once you pick a layout, and no bits are invented for the ones we cannot place.

Where the numbers come from

Scope. This table keeps only layouts whose field split is published somewhere. A general format table such as cardinfo.barkweb.com.au lists 70, but most of those are vendor-private or regional, or publish no bit map at all. A layout with no published bit map could only be filled in by guesswork, so it stays out until someone publishes one.

Every row is compiled from vendor manuals and third-party documentation, and every row carries a confidence level. High means two or more independent public sources agree and the layout has been checked against a real frame; medium means a single third-party source, or sources that disagree on a detail; low means the field widths are known but the bit positions were not published — do not build hardware around those.

The rows live in one JSON file and this page is generated from it, so a format cannot be added to the table without existing in the data, and a row cannot drift from the data it came from. If a row is wrong, the fix belongs in the data; corrections are genuinely welcome through the contact page.