{"id":2013,"date":"2022-12-05T13:37:05","date_gmt":"2022-12-05T05:37:05","guid":{"rendered":"https:\/\/www.toptaggroup.com\/adweb_products\/uncategorized\/125khz-rfid-em4100-key-fobs\/"},"modified":"2026-07-16T17:54:43","modified_gmt":"2026-07-16T09:54:43","slug":"125khz-rfid-em4100-key-fobs","status":"publish","type":"products","link":"https:\/\/www.toptaggroup.com\/da\/products\/125khz-rfid-em4100-key-fobs\/","title":{"rendered":"125 kHz RFID EM4100 n\u00f8glebrikker"},"content":{"rendered":"

125khz RFID EM4100 Key Fobs \u2014 Works with 40+ Reader Brands Out of the Box<\/h2>\n

125 kHz RFID EM4100 n\u00f8glebrikker<\/strong> are the most-deployed low-frequency access credentials in the world \u2014 ABS-cased 125 kHz proximity tokens pre-programmed with a 40-bit read-only ID that any Manchester-encoded 125 kHz reader will recognise. If your building already has a working 125 kHz door reader, these fobs almost certainly read on it. The compatibility question is not “will they work” \u2014 it is “will you get 125khz RFID EM4100 Key Fobs from a supplier who has actually verified them against the specific reader family your customer is running.”<\/p>\n

This page is the reader ecosystem reference for procurement buyers, locksmiths, distributors, and access control integrators evaluating a bulk source of 125khz RFID EM4100 Key Fobs. Every brand listed below has been physically tested on our QC bench with a live production sample \u2014 not copied from a datasheet.<\/p>\n

<\/p>\n

\n

\"125khz
125 kHz RFID EM4100 n\u00f8glefob \u2014 ABS-n\u00e6rheds-tokener i bl\u00e5, r\u00f8d, sort, gul, gr\u00f8n, hvid \u2014 forprogrammeret med 40-bit ID, kompatibel med universelle 125 kHz-l\u00e6sere<\/figcaption><\/figure>
125khz EM4100 key fobs in 7 stock colours. ABS shell, split-ring hole, 40-bit factory UID. Compatible with the majority of 125 kHz access control readers deployed worldwide.<\/figcaption><\/figure>\n

The Compatibility Problem in 125 kHz Procurement<\/h2>\n

125 kHz is the oldest widely deployed RFID frequency in commercial access control. It was standardised before ISO 14443, before MIFARE, before EM4100 competitors like Hitag and Indala existed. The result is a legacy installed base measured in hundreds of millions of readers, distributed across roughly 25 years of building infrastructure. A distributor selling replacement fobs to an office building today is not selling into a greenfield deployment \u2014 they are selling into a system that was probably installed in 2011 by an integrator that has since gone out of business, with no documentation of which reader family or protocol variant is running behind the panel.<\/p>\n

This is why fob compatibility fails. The fob technically emits a valid 40-bit EM4100 Manchester-encoded ID, but the panel is programmed to expect a specific card format (26-bit Wiegand, 34-bit HID, custom facility code + card number split), and the fob’s raw ID does not parse cleanly into that format. The end customer complains that “the new fobs don’t work” when in reality the fobs work, the reader works, and the panel simply cannot decode the ID structure it was configured for a decade ago.<\/p>\n

Our solution is not a magic universal fob. It is a verified compatibility matrix \u2014 a bench-tested list of readers, panels, and format configurations where the fobs are known to read and enrol without troubleshooting. Ship into anything on that list, and installation time drops from 2 hours of debug to under 15 minutes.<\/p>\n

Verified Reader Ecosystem<\/h2>\n

The table below is a working extract of our compatibility log \u2014 the full log is available on request for verified B2B accounts. Every entry has been tested on a physical reader at our Shenzhen QC bench within the past 24 months.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Brand<\/th>\nReader Family \/ Model<\/th>\nRead Range (cm)<\/th>\nFormat Support<\/th>\nStatus<\/th>\n<\/tr>\n
HID Global<\/td>\nProxPro II, ProxPoint Plus, MiniProx<\/td>\n6\u201310<\/td>\n26-bit Wiegand output<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Iron Logic (CIS)<\/td>\nMatrix-II, Matrix-III, Z-2 USB<\/td>\n4\u20138<\/td>\nEM Marine raw<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Bolid<\/td>\nProxy-5MSG, Proxy-5MSB, S2000-2<\/td>\n5\u20138<\/td>\nTouch Memory \/ Wiegand-26<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
ZKTeco<\/td>\nKR500, KR600E, ProBio, F18<\/td>\n5\u20138<\/td>\nWiegand-26 \/ 34<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Anviz<\/td>\nM5, T5S, VP30<\/td>\n4\u20137<\/td>\nWiegand-26<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Suprema<\/td>\nBioEntry Plus, BioLite N2 (125 kHz variant)<\/td>\n3\u20136<\/td>\nWiegand-26 \/ RS-485<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Hikvision<\/td>\nDS-K1102M, DS-K1108M<\/td>\n4\u20136<\/td>\nWiegand-26 \/ 34<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Dahua<\/td>\nASR1101A, ASR2101A<\/td>\n4\u20137<\/td>\nWiegand-26<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Rubezh<\/td>\nRS-100, RS-101, Cardholder-1<\/td>\n4\u20138<\/td>\nTouch Memory \/ Wiegand<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Honeywell<\/td>\nOmniProx OP10HON, OP30HON<\/td>\n6\u201310<\/td>\nWiegand-26 \/ 34<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Rosslare<\/td>\nAY-K12, AYC-E55<\/td>\n5\u20138<\/td>\nWiegand \/ Clock&Data<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Farpointe Data<\/td>\nP-300, P-320<\/td>\n5\u20138<\/td>\nWiegand-26<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Nedap<\/td>\nN.Reader (125 kHz variant)<\/td>\n4\u20137<\/td>\nWiegand \/ OSDP<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Generic OEM<\/td>\nAny Wiegand-26 output 125 kHz reader<\/td>\nvaries<\/td>\nWiegand-26<\/td>\n\u2705 Verified<\/td>\n<\/tr>\n
Legacy Indala<\/td>\nIndala 26-bit \/ 27-bit proprietary<\/td>\n\u2014<\/td>\nNot compatible<\/td>\n\u274c Different protocol<\/td>\n<\/tr>\n
AWID<\/td>\nAWID 26-bit \/ 34-bit<\/td>\n\u2014<\/td>\nNot compatible<\/td>\n\u274c Different encoding<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The two \u274c entries at the bottom are there deliberately. Indala and AWID formats are not EM4100-compatible \u2014 they are proprietary 125 kHz variants that emit a different bit structure. A distributor who ships an EM4100 fob into an Indala-based site will get a return. Selling into the wrong ecosystem is the single largest cost centre in 125 kHz distribution; knowing where not<\/em> to sell matters as much as knowing where to sell.<\/p>\n

EM4100, EM4200, TK4100 \u2014 Which Chip Actually Ships?<\/h2>\n

“EM4100” is now a category label rather than a single chip. The original EM Microelectronic EM4100 die has been replaced in most current production by its second-generation replacements \u2014 EM4200 and the widely available compatible TK4100 \u2014 which are pin-for-pin drop-ins with identical 40-bit Manchester-encoded output at 125 kHz. From a reader’s perspective, they are indistinguishable. Our standard 125khz RFID EM4100 Key Fobs ship with EM4200 or TK4100 chips, depending on component availability, and every batch is verified against the same reader compatibility matrix before shipment.<\/p>\n

Customers who require the original EM4100 die specifically \u2014 usually for regulatory compliance with a legacy system certified against a specific chip revision \u2014 can order it as a special-run configuration with a 500 pc MOQ and a 21-day lead time. For the 95% of customers who simply need a working 125 kHz fob, EM4200 \/ TK4100 is the correct spec, costs the same, and reads on every reader in the compatibility table above.<\/p>\n

Software \/ SDK \/ API Support<\/h2>\n

Because the EM4100 protocol is read-only and emits a fixed factory-programmed UID, there is no chip-side software layer to support \u2014 the fob simply broadcasts its ID whenever it enters the reader field. The software integration happens at the reader and panel side. Our fobs are validated against the following panel software platforms:<\/p>\n