ICODE and ISO 15693: The Long-Range NFC You Rarely See
ISO 15693 is the vicinity-card standard behind NXP's ICODE tags — built for reading at a distance, not a deliberate tap. Here's how it differs from the NTAG/MIFARE tags you already know, where it actually shows up, and what it takes for a phone to read one.
What It Is
ISO 15693 is an HF radio standard for "vicinity" tags — ones designed to be read from further away than a typical NFC tap, instead of pressed right against a reader. NXP's ICODE chips are the most common implementation. If you've ever checked out a library book or scanned a ski pass without lining anything up precisely, you've probably used one without knowing it. In NFC Forum terms, this standard is Type 5, and phones refer to it as NFC-V — separate from the NFC-A tags (NTAG, MIFARE) that most consumer NFC apps are built around.
How It Actually Works
Vicinity vs. Proximity
Standard NFC tags like NTAG213 or MIFARE Ultralight run on ISO 14443-A, a "proximity card" protocol that expects a tag to sit millimeters from the reader. ISO 15693 trades that closeness for range: it still operates at 13.56 MHz, but uses a weaker magnetic field and a slower data rate — 1.65 to 26.48 kbit/s, depending on encoding — in exchange for a read distance up to 1 to 1.5 meters with a dedicated HF reader. That tradeoff is deliberate. Vicinity cards were never meant to compete with proximity tags on speed; they were built to be read without careful placement. For the full picture of how NFC Forum tag types 1 through 5 map to these underlying standards, that's worth a separate read.
Where ICODE Fits
NXP's ICODE 3 chip is certified NFC Forum Type 5 Tag compliant, with a read rate up to 212 kbit/s and 2400 bits of user memory. The line is built for cross-range use — the same tag can be picked up from across a gate by a fixed reader, or tapped directly with a phone at close range.
Where You'll See It
ISO 15693 shows up wherever a system needs to read a tag reliably without a person carefully aligning it: libraries tracking books, ski resorts validating lift passes, retailers doing item-level inventory counts, logistics operations tracking pallets or assets as they move through a gate. Healthcare systems use it too, for similar reasons. It's a different design goal than the close, deliberate tap most NFC tags rely on — ISO 15693 is built for volume and distance, not precision.
Tips, Gotchas, and a Quick How-To with NFCore
Not every phone-based "NFC reader" app can see ISO 15693 tags, and that trips people up. On iPhone, Core NFC supports ISO 15693 through a dedicated interface, but reading one means the app has to start a foreground session just for it — there's no passive background tap the way there is for NDEF-formatted NTAG tags. Android handles it through a separate NfcV technology class, so an app has to speak the raw ISO 15693 command set rather than just parse NDEF data.
NFCore reads ICODE and other ISO 15693 tags directly, including the tag's UID and memory contents — open the app, hold your phone near the tag, and start a scan from the Tag Inspector. If a general NFC app you've tried comes up empty on a library tag or a ski pass, this is usually why.
Frequently Asked Questions
Is ICODE the same thing as ISO 15693?
ICODE is NXP's chip family that implements the ISO 15693 standard — ISO 15693 is the international standard, and ICODE is one manufacturer's product line built to it. Other vendors make ISO 15693 chips too, but ICODE is the one you'll run into most often.
Will my phone read an ICODE / ISO 15693 tag?
Most modern iPhones and Android phones can read ISO 15693 tags, but not the same way they read an NTAG213 sticker. There's no automatic background tap — the app has to specifically start an ISO 15693 (NFC-V) session, which is why a general-purpose tag reader needs explicit support for it.
What's the real-world read range of an ISO 15693 tag?
With a dedicated long-range HF reader, up to about 1 to 1.5 meters. With a phone, it's closer to a standard tap distance — a few centimeters — because a phone's antenna and power output are much smaller than a fixed reader's.
Why would anyone use ISO 15693 instead of NTAG or MIFARE?
Range and read reliability at a distance. Libraries, ski resorts, and logistics operations need to read a tag without lining it up precisely against a reader — ISO 15693's vicinity-card design was built for exactly that, where NTAG-style tags are built for a close, deliberate tap.
The Bottom Line
ISO 15693 and the ICODE tags built on it are the long-range half of the NFC world — the standard behind library books, ski passes, and logistics tags that get read from a few feet away instead of a careful tap. It's a different design than the NTAG and MIFARE tags most people picture when they hear "NFC," but it's built on the same 13.56 MHz frequency and increasingly shows up in the same phones. As more everyday apps add ISO 15693 support, seeing "NFC-V" or "Type 5" on a tag won't stay a niche case for much longer.