HF / NFC Legacy 
MIFARE Ultralight C
For ticketing and loyalty applications that additionally require 3DES authentication.
Security 3DES
Memory 192 B
MIFARE Ultralight® EV1: Technical Data, Security and Use
The MIFARE Ultralight EV1 is a contactless HF RFID chip for 13.56 MHz. The manufacturer is NXP Semiconductors. The chip operates according to ISO/IEC 14443 Type A and is designed as an NFC Forum Type 2 Tag. It was developed primarily for contactless tickets with a limited period of use. Typical applications are public transport tickets, day and event tickets and loyalty applications.
MIFARE Ultralight EV1 is available with 48 bytes or 128 bytes of freely usable user memory. The chip supports configurable 32-bit password protection, three independent 24-bit counters and an ECC-based originality signature. It does not offer strong cryptographic authentication. For simple tickets and NFC applications, this is often sufficient. Applications with high security requirements need a different chip family.
| Feature | Value |
|---|---|
| Manufacturer | NXP Semiconductors |
| Product family | MIFARE Ultralight EV1 |
| Type designations | MF0UL11 / MF0UL21 |
| RFID class | HF / NFC |
| Frequency | 13.56 MHz |
| Standard | ISO/IEC 14443 Type A |
| Data rate | 106 kbit/s |
| EEPROM | 80 bytes (MF0UL11) / 164 bytes (MF0UL21) |
| User memory | 48 bytes (MF0UL11) / 128 bytes (MF0UL21) |
| Memory structure | 20 or 41 pages of 4 bytes each |
| Authentication | 32-bit password protection with PWD_AUTH |
| Encryption | None |
| Originality Check | ECC-based NXP originality signature |
| Counters | 3 independent 24-bit one-way counters |
| UID | Unique 7-byte UID |
| Anti-collision | Yes |
| Read range | up to 100 mm according to NXP, depending on antenna and reader |
| Write cycles | At least 100,000 at 22 °C |
| Data retention | At least 10 years at 22 °C |
| Smartphone NFC | Very good with NFC Forum/NDEF-compliant use |
| Product status at NXP | Active |
| Typical media | RFID card, ticket, wristband, tag and label |
| Security rating | Basic protection |
| Recommendation |
For tickets, events and simple NFC applications |
NXP offers MIFARE Ultralight EV1 in two memory variants. MF0UL11 has a total of 80 bytes of EEPROM with 48 bytes of freely usable memory, MF0UL21 a total of 164 bytes of EEPROM with 128 bytes of user memory. The remaining memory contains UID, lock, OTP and configuration areas, among others. Both variants support a 7-byte UID, three independent 24-bit counters, 32-bit password protection and an ECC-based originality signature.
Typical Applications and Media Formats
MIFARE Ultralight EV1 was developed for applications in which a contactless medium is used only for a limited time or a manageable number of transactions. NXP names public transport, event ticketing and loyalty as core applications.
These include, for example:
- single and day tickets for public transport
- admission tickets for events, stadiums and leisure facilities
- visitor and day passes
- simple loyalty applications
- NFC tags with small NDEF records
- RFID media used for a limited time
Suitable media are RFID cards, paper and plastic tickets, wristbands as well as tags and labels. The small chip size and the available input capacitances of 17 pF and 50 pF allow for different inlay and antenna designs.
Security of MIFARE Ultralight EV1
Security level: Basic protection
MIFARE Ultralight EV1 has no encryption such as AES or 3DES. Memory areas can be protected against reading and/or writing using a 32-bit password . After a successful password check, the chip responds with a 16-bit PACK. Optionally, the number of failed password attempts can be limited.
In the data sheet, NXP explicitly points out that this password check does not provide a high level of security . It is mainly intended to prevent unintended or simple unauthorized memory access.
The ECC-based originality signature can be used to check whether a chip originates from NXP. However, it does not encrypt any user data and is no substitute for cryptographic authentication.
This feature set is suitable for simple tickets, NFC content and applications without high security requirements. For security-critical access control, protected stored value or sensitive personal data, a chip with cryptographic authentication should be considered.
Advantages and Disadvantages of MIFARE Ultralight EV1
| Advantages | Disadvantages |
|---|---|
| NFC Forum Type 2 Tag compatible | No cryptographic encryption |
| Good smartphone support for NDEF | 32-bit password offers only basic protection |
| 48 or 128 bytes of freely usable memory | Little memory for more extensive applications |
| Three independent 24-bit counters | Not intended for security-critical access control |
| 7-byte UID and NXP originality signature | No application or file system |
| Designed for small ticket and inlay formats | Significantly smaller range of functions than MIFARE DESFire |
Alternatives to MIFARE Ultralight EV1
Depending on the application, memory requirements and security needs, other chip types may be better suited.
HF / NFC Recommendation 
NTAG 213 / 215 / 216
For NFC applications with smartphones and larger NDEF content.
Security PWD
Memory 144–888 B
HF / NFC Recommendation 
MIFARE DESFire EV3
For access control, ID card and ticketing applications with higher security requirements.
Security AES-128
Memory 2 / 4 / 8 / 16 KB
Frequently Asked Questions about MIFARE Ultralight EV1
How much memory does MIFARE Ultralight EV1 have?
MIFARE Ultralight EV1 is available in two memory variants. MF0UL11 has 48 bytes of user memory, distributed over twelve pages of four bytes each. MF0UL21 has 128 bytes of user memory on 32 pages.
The total EEPROM is larger. NXP specifies 640 bits or 80 bytes for MF0UL11 and 1,312 bits or 164 bytes for MF0UL21. In addition to the user memory, this includes the UID, OTP, lock and configuration areas.
What is the difference between MF0UL11 and MF0UL21?
The main difference is the memory size.
| Feature | MF0UL11 | MF0UL21 |
|---|---|---|
| Total EEPROM | 80 bytes | 164 bytes |
| User Memory | 48 bytes | 128 bytes |
| User pages | 12 | 32 |
| Page size | 4 bytes | 4 bytes |
| UID | 7 bytes | 7 bytes |
| Password protection | 32 bits | 32 bits |
| Counters | 3 × 24 bits | 3 × 24 bits |
The larger MF0UL21 variant is suitable if a ticket or NFC tag has to store more user data. Security functions and basic communication are the same for both variants.
How secure is MIFARE Ultralight EV1?
The chip offers 32-bit password protection, lock bits, a 7-byte UID and an ECC-based originality signature. There is no encryption of communication with AES or 3DES. NXP itself explicitly does not describe the password check as protection for applications with high security needs.
MIFARE Ultralight EV1 is therefore suitable for tickets and NFC applications where simple protection against unwanted reading or writing is sufficient. For security-critical access control or protected stored value, a chip family with cryptographic authentication should be used.
Can MIFARE Ultralight EV1 be read with a smartphone?
Yes, very well for standardized NFC applications. MIFARE Ultralight EV1 is NFC Forum Type 2 Tag compatible. If the memory is correctly formatted with NDEF data, it can store URLs or other small NFC content, for example. NXP itself includes a MIFARE Ultralight EV1 card configured with NDEF as an NFC Forum Type 2 Tag in an NFC demo kit.
Android requires support for NDEF on NFC Forum Tag Types 1 to 4 for devices with NFC and explicitly names MIFARE Ultralight as an example of Type 2. Apple Core NFC can read and write NDEF tags of types 1 to 5.
Ultralight EV1 is sufficient for very small NDEF records. If longer URLs, contact details or more extensive content are required, NTAG213, NTAG215 or NTAG216 offer more memory.
Which readers support MIFARE Ultralight EV1?
A reader must operate at 13.56 MHz and ISO/IEC 14443 Type A and support the MIFARE Ultralight EV1 commands. The chip communicates at 106 kbit/s. NXP specifies an operating distance of up to 100 mm, with the antenna geometry and reader configuration determining the actual range.
For existing ticketing or reader systems, it should be checked before ordering whether the required functions such as password check, Fast Read or counters are supported.
What is the difference between MIFARE Ultralight EV1 and MIFARE Ultralight C?
Both chips are aimed at simple contactless ticketing and identification applications. MIFARE Ultralight C adds 3DES authentication to the concept and thus offers stronger cryptographic protection than the 32-bit password mechanism of the Ultralight EV1.
MIFARE Ultralight EV1, on the other hand, offers functions such as three independent 24-bit counters, ECC originality check and NFC Forum Type 2 Tag compatibility. Which variant is suitable depends mainly on whether simple access protection is sufficient or cryptographic authentication is required.
What is the difference between MIFARE Ultralight EV1 and NTAG213?
Both chips can be used as NFC Forum Type 2 Tags for NDEF applications. The NTAG213 offers 144 bytes of user memory and is more strongly geared toward NFC applications with smartphones. MIFARE Ultralight EV1, on the other hand, was developed primarily for contactless tickets with a limited period of use.
For an event ticket with little data and counter functions, Ultralight EV1 can be a good fit. For NFC marketing, digital business cards or product information, NTAG213 is usually the more obvious choice.
Can MIFARE Ultralight EV1 be permanently write-protected?
Yes. The chip has programmable lock bits. These can be used to permanently lock memory areas against further write access. For the first 512 bits, the lock works page by page; for the extended memory area of the larger variant, it works for two pages at a time. The 32-bit OTP area can also only be programmed in one direction.
Once a permanent write lock has been set, it cannot be reversed. It should therefore only be set after personalization has been completed.
Is MIFARE Ultralight EV1 still being produced?
Yes. NXP currently lists MIFARE Ultralight EV1 with the product status “Active”. Unlike MIFARE Classic, the current product page does not show a “not recommended for new designs” notice.
The chip therefore remains a current option for simple contactless tickets and applications that can manage with the available memory and the 32-bit password protection.
Technical sources
Data as of: September 2026
The technical information is based on the NXP data sheet MF0ULX1, MIFARE Ultralight EV1 – Contactless ticket IC, Rev. 3.3 dated 9 April 2019, the current NXP product page and the NXP fact sheet on MIFARE Ultralight EV1.
The information on smartphone support is based on the Android NDEF documentation and Apple's Core NFC documentation.
Trademark notice
MIFARE and MIFARE Ultralight are trademarks of NXP B.V.
The spelling follows the MIFARE Trademark and Branding Guidelines, Rev. 5.2 dated 10 March 2025. For the first or most prominent mention, NXP prescribes the form MIFARE Ultralight®. “EV1” may be used as a defined suffix. The trademark may not be separated or altered with hyphens.