Enterprise

Nedap Cards Explained: Magna, NeXS, TRANSIT & uPASS

Security ID Systems ·

A Nedap card is a proprietary RFID access credential engineered for use with Nedap's AEOS physical-access platform, encoding a 128-bit ASK/Manchester data structure that includes a subtype field and customer-specific code. The Nedap credential family spans four distinct product lines — Magna and NeXS for low-frequency proximity, TRANSIT for long-range vehicle identification, and uPASS for UHF pedestrian and vehicle applications — each designed to serve a different read-range and deployment scenario within the same enterprise platform. Compatible replacements for Nedap readers and AEOS-controlled installations are available across all major product lines.

Nedap, AEOS and the Product Family

Nedap is a Dutch technology company whose AEOS platform is one of the more sophisticated enterprise access-control systems in use across European commercial real estate, data centres, and infrastructure sites. Unlike systems that treat the card as a simple identifier, AEOS is a policy-driven architecture: the credential carries enough encoded structure that the reader can verify it belongs to the correct customer deployment before even consulting the controller. That architectural decision has direct implications for which credential types will operate in a given installation.

The AEOS credential portfolio reflects three decades of product evolution. The original Magna 125 kHz proximity line was later joined by NeXS, which shares the same LF encoding standard but is produced on updated carrier stock. For vehicle-access applications, TRANSIT passive long-range tags and the UHF-based uPASS family handle read distances that a wallet card could never achieve. The Combi variant bridges formats, embedding a UHF antenna, a 125 kHz coil, and a high-frequency smart chip on a single credential — useful where an organisation needs one badge to satisfy multiple reader types across a mixed estate.

Nedap occupies what access-control procurement teams recognise as an enterprise-tier proprietary format: the encoding depth, the customer-code layering, and the global installed base make compatible-credential supply a specialised exercise. The depth of that specialisation — selecting the right blank substrate, encoding the correct data structure, verifying the output at the reader's Wiegand or OSDP port — is precisely the installed-reader lock-in that keeps many facilities teams tethered to original-vendor supply chains longer than necessary. It is a format Security ID Systems specifically stocks. Facilities managers who need enterprise-grade proprietary format replacements that are compatible with their installed readers can obtain Nedap-format credentials without routing through the original vendor's distribution channel.

The 128-Bit Magna and NeXS Proximity Format

The technical signature of a Nedap LF credential is its 128-bit data payload transmitted using ASK modulation with Manchester encoding at 125 kHz. That bit depth distinguishes it immediately from the more common 26-bit Wiegand cards found in mid-market installations: where a standard 26-bit card carries a facility code and card number in roughly 40 usable bits, the Nedap format encodes a subtype identifier, a customer code, and an extended card serial number across 128 bits. Readers programmed for Nedap format will reject a card that presents the wrong subtype, regardless of whether the card number falls within an expected range.

Magna is the legacy designation for the original Nedap LF line; NeXS is the current equivalent, produced on thinner ISO-format stock with the same underlying encoding. From a reader-compatibility standpoint the two are interchangeable in most AEOS deployments, and compatible credentials supplied against a NeXS specification will operate in readers that were originally supplied with Magna cards. If you are unsure which variant your installation uses, our access card format identification guide walks through the physical and electronic markers to check.

For production of compatible LF Nedap credentials, the blank substrate must carry a writable transponder capable of emulating the 128-bit ASK/Manchester data structure — T5577, Q5, and EM4305 chips are the standard writable LF transponders used in this context. The encoding data is read from a sample credential presented to our equipment, or is drawn from a customer-supplied site programming file that specifies the subtype, customer code, and card-number range; the finished card presents identically to the original at the reader's Wiegand or OSDP output. Facilities teams managing large AEOS estates often source Nedap compatible proximity cards in bulk to cover attrition and new-starters without waiting on original-equipment lead times.

The 128-bit structure also means that producing a compatible requires a defined mapping process: every field in the data payload must be correctly placed for the reader to accept the credential. This is not a commodity duplication task — it demands the same systematic approach used for other enterprise-tier formats such as Gallagher compatible proximity cards or Lenel 42-bit compatible cards. The reward for that precision is a replacement credential that is electrically indistinguishable from the original at the reader antenna.

TRANSIT Long-Range and uPASS UHF

TRANSIT is Nedap's passive long-range credential family, designed for vehicle-access and barrier-control applications where read distances of several metres are required. TRANSIT tags typically operate at 125 kHz but are physically much larger than a wallet card — windscreen-mount transponders and dashboard tags are the most common form factors. The extended antenna geometry is what delivers the read range; the underlying encoding is consistent with the Nedap LF data model, so the same AEOS controller infrastructure manages both pedestrian-badge and vehicle-tag reads.

uPASS operates in the UHF band (typically 865–868 MHz in the ETSI region or 902–928 MHz FCC), achieving read distances beyond what any LF technology can sustain — practical vehicle-access systems based on uPASS frequently perform reliable reads at five to ten metres. The uPASS product line includes both vehicle-mounted tags and handheld credentials for pedestrian UHF lanes. Because UHF credential replacement requires a UHF-capable blank rather than the LF substrates used for Magna and NeXS, sourcing compatible uPASS tags is a different supply exercise from sourcing LF cards.

The Combi credential layers all three technologies — UHF, 125 kHz LF, and an HF smart chip — onto a single ISO card body. An employee in a Combi deployment carries one badge that satisfies the pedestrian door reader (LF prox), the car-park barrier antenna (UHF), and any HF smart-card reader in the same estate. The Combi form is the most complex compatible-credential request we receive for the Nedap family, and it requires careful specification of which bands are in use at the target site before a compatible blank can be selected.

It is worth noting that the uPASS UHF line is used not only for vehicle access but increasingly for high-throughput pedestrian lanes in stadiums, transport hubs, and large campuses where LF read speeds are insufficient. In those deployments a handheld UHF card or wristband credential operates on the same AEOS controller platform as the LF pedestrian doors, giving the access-control team a single policy engine across radically different read-range requirements. Compatible UHF credentials for these applications follow the same ISO 18000-6C supply path as windscreen TRANSIT tags, with EPC data sourced from the site's enrollment records.

Producing Compatible Nedap Credentials by Band

Low-frequency Magna and NeXS compatibles are produced on T5577, Q5, or EM4305 writable transponders. These chips implement the same 128-bit ASK/Manchester protocol the Nedap reader expects, and when correctly programmed they are electrically indistinguishable from the original credential at the reader's antenna. The programming input is either a sample card presented to our encoding equipment — from which our tools read the site-specific data values — or a data file from the end customer specifying the subtype, site code, and card-number range. The finished credential passes through a verification read before it ships.

UHF-band uPASS compatible tags require a UHF-capable blank — typically an ISO 18000-6C (EPC Gen2) substrate tuned to the correct frequency band for the installation geography. The Nedap uPASS reader is programmed to look for specific EPC data structures; the compatible tag must be written with EPC content that matches the site's enrollment data. This is more complex than LF programming and requires site-specific data to be provided by the customer. Our proximity card frequencies and standards glossary covers the frequency band and protocol distinctions that matter when specifying a UHF compatible.

Combi credential production combines both supply paths: an LF-capable blank is selected for the 125 kHz portion, the UHF antenna is integrated into the same laminate, and the HF chip layer is enrolled separately if the smart-card function is active. Not every site activates all three layers of a Combi credential, so it is important to confirm which bands are reader-active before placing an order. Customers unfamiliar with how their Nedap estate is configured can reference our compatible versus genuine access cards buyer's guide for background on what information needs to be recorded from a working sample before a compatible can be specified.

Across all bands, the 125 kHz LF proximity format category covers the Magna and NeXS lines alongside other enterprise LF formats. Nedap's 128-bit structure makes it more selective than commodity 26-bit formats but the supply process follows the same logic: present a working credential or supply the site encoding data, and compatible replacements can be produced in standard ISO card, key fob, or tag form factors depending on what the application demands. For estates that also deploy Hitag2 compatible cards and fobs or Avigilon 56-bit compatible cards, multi-format orders are handled in a single transaction.

Ordering Compatible Nedap Cards and Tags

Ordering compatible Nedap proximity credentials begins with identifying which product line is in use and, for LF formats, whether the installation is Magna or NeXS. In practice the two share encoding and either type of compatible will operate in both reader variants, but confirming the physical form factor — ISO card, clamshell fob, windscreen tag, or handheld UHF credential — ensures the replacement suits the user's carry method and the reader's mounting location.

For accounts running mixed estates — Nedap on some doors, other enterprise formats on others — we can supply compatible credentials for multiple formats in a single order. Gallagher compatible proximity cards and Lenel 42-bit compatible cards are examples of enterprise-proprietary formats that coexist with Nedap in large multi-system installations. Consolidating credential supply across formats reduces the number of vendor relationships a facilities team has to manage and keeps re-order lead times predictable.

If a site is moving toward a multi-technology estate or adding UHF vehicle access alongside an existing LF pedestrian system, the Combi format is worth evaluating. It eliminates the need to carry separate credentials for different reader types and simplifies badge stock management — one card SKU covers all access points. Discuss the active bands with your access-control integrator before ordering to confirm that the HF smart-card layer is or is not in active use. Contact our technical team to discuss compatible Nedap credential specifications for your installation, or browse our full compatible access credential catalogue for available format and form-factor options.

For sites that are planning a phased migration — for example, introducing UHF vehicle access while retaining the existing Magna or NeXS pedestrian infrastructure — Combi credentials can serve as a transitional badge stock that works across both generations of reader without issuing separate credentials for each access point. This approach is particularly common in large commercial campuses or corporate headquarters where a vehicle-access upgrade is approved ahead of a full pedestrian-system refresh. Software House CCOTZ 37-bit compatible cards are another enterprise-tier format frequently encountered in the same large-estate deployments as Nedap, and our team handles both in parallel orders.

Security ID Systems is an independent manufacturer and supplier of compatible access-control credentials and is not affiliated with, authorized by, or endorsed by Nedap.

Nedap AEOS Credential Product Lines: Key Technical Specifications

Product LineFrequency / BandEncodingTypical Form FactorPrimary ApplicationCompatible Blank Type
Magna (legacy LF)125 kHz128-bit ASK/Manchester, subtype + customer codeISO card, clamshell fobPedestrian door accessT5577 / Q5 / EM4305
NeXS (current LF)125 kHz128-bit ASK/Manchester, same as MagnaISO card, slim fobPedestrian door accessT5577 / Q5 / EM4305
TRANSIT (long-range LF)125 kHzNedap LF data model, extended antennaWindscreen tag, dashboard mountVehicle barrier / car-parkLF long-range writable transponder
uPASS (UHF)865–928 MHz UHF (ETSI / FCC)EPC Gen2 / ISO 18000-6C with Nedap EPC structureWindscreen tag, handheld cardVehicle access, long-range pedestrian lanesISO 18000-6C UHF blank
Combi125 kHz + UHF + HF (13.56 MHz)All three layers encoded independentlyISO cardMixed-estate single-badge deploymentsMulti-technology composite blank

Frequently asked questions

What format is a Nedap card?

A Nedap card uses a 128-bit ASK/Manchester encoding structure transmitted at 125 kHz for the LF Magna and NeXS product lines. The data payload includes a subtype identifier and a customer-specific code that AEOS readers use to verify the credential belongs to the correct installation. UHF uPASS credentials use EPC Gen2 encoding in the 865–928 MHz band, and Combi cards layer LF, UHF, and HF on a single substrate.

What is the difference between Nedap Magna and NeXS?

Magna is the legacy Nedap LF proximity line; NeXS is the current equivalent, produced on updated ISO-format carrier stock. Both use the same 128-bit ASK/Manchester encoding at 125 kHz, and compatible credentials produced for one are generally compatible with readers originally supplied with the other. The practical difference is form factor and production vintage rather than any change to the underlying data structure.

Can a Nedap uPASS UHF tag be replaced with a compatible?

Yes. Compatible uPASS UHF tags are produced on ISO 18000-6C (EPC Gen2) blanks tuned to the correct frequency band — ETSI 865–868 MHz for European installations or FCC 902–928 MHz for North American sites. The blank is written with the EPC data structure the Nedap reader expects, sourced from the customer's site enrollment data. Because UHF programming is site-specific, a sample tag or data file is required to produce compatible replacements.

Does Nedap use 125 kHz or UHF?

Nedap uses both frequencies across its credential family. The Magna and NeXS pedestrian-access lines operate at 125 kHz LF, while the uPASS and TRANSIT vehicle-access lines use UHF (865–928 MHz) for long-range reads. The Combi credential integrates 125 kHz, UHF, and 13.56 MHz HF smart-card technology on a single card for estates where multiple reader types are deployed.

What is a Nedap Combi card?

A Nedap Combi card is a multi-technology credential that combines a 125 kHz LF proximity antenna for standard door readers, a UHF antenna for long-range vehicle or pedestrian-lane reads, and a 13.56 MHz HF smart chip on a single ISO card body. It allows one badge to satisfy all reader types across a mixed Nedap estate, simplifying both the user experience and badge-stock management for facilities teams.

Are compatible Nedap cards available for the full product range?

Compatible credentials are available for the Magna, NeXS, and uPASS product lines, as well as for Combi configurations where the active technology layers are confirmed. LF Magna and NeXS compatibles are produced on T5577/Q5/EM4305 writable substrates; UHF uPASS compatibles require a UHF-capable blank and site EPC data. Combi production is handled as a custom order specifying which bands are active in the target installation.

How do I identify whether my site uses Nedap Magna or NeXS?

In most cases the reader behaviour is the same for both Magna and NeXS, since they share the same 128-bit LF encoding. Physical identification comes from the card body markings — NeXS cards typically carry that product name, while older Magna stock may be unlabelled or marked with the Magna designation. Our access card format identification guide covers the physical and electronic checks for distinguishing Nedap LF variants from other 125 kHz formats deployed on the same site.

What information is needed to order compatible Nedap LF credentials?

For Magna and NeXS LF orders, either a sample credential from the installation or a data file specifying the subtype, customer code, and card-number range is required. Our encoding equipment reads the relevant field values from the sample card; no additional documentation is needed when a working credential is provided. For UHF uPASS orders, the site's EPC enrollment data must be supplied by the customer or their access-control integrator, as UHF programming is site-specific and cannot be inferred from a single sample alone.

Request a quote

Can't find your format? Email the specialists.

Send the part number printed on your card or a photo of the reader. We confirm compatibility before you order — and we cover the specialist formats nobody else lists.