WB505 · woven and printed event straps
A branded strap. A separate tag. Your choice of closure.
RFID fabric wristbands combine a polyester strap, separate PVC RFID tag and sliding closure. The published WB505 strap reference is 350 × 15 mm; a 35 × 25 mm tag is listed for the event format. Choose woven artwork or heat-sublimation printing, then a one-way slider or reusable bead. LF and HF chip options support different readers and event workflows.
Download technical reference (PDF) ↓
Published product specifications
The supplier lists WB505 with a 350 × 15 mm strap. Its event-format reference uses a 35 × 25 mm PVC tag. The tag passes over the strap through two slots; the separate slider adjusts the band.
Flat length is not wrist circumference. The tails and fastening allowance use part of the strap length. Match the closed fit to the wearer’s wrist measurement.
Dimension and construction sources: WB505 cloth wristband ↗Event strap and tag reference ↗
Configuration catalogue
The published WB505 fabric format uses a 350 × 15 mm strap. Choose the artwork method and closure below; these are configuration references, with the finished chip, tag outline and print layout identified on the order.
350 × 15 mm
350 × 15 mm
350 × 15 mm
The one-way slider and reusable bead are separate closure choices. A sample removal check establishes how the chosen band behaves when pulled, cut or refitted; ticket cancellation remains a software function.
Artwork and identification
Choose the artwork method before preparing the production file. The strap and PVC face have different usable areas, and the fabric can move or fold during wear.
The tag face provides a flat area for a QR code. Printed artwork and the RFID credential can reference the same ticket record.
The supplier lists up to 8 yarn colors. Letters and shapes are formed by the yarn pattern, producing visible textile texture. Favor clear lettering and bold motifs over tiny text.
Printing adds multicolor artwork to the fabric surface. This route accommodates gradients and detailed graphics; approve the colors and orientation on the actual strap.
The supplier lists logo printing, laser-marked UID numbers, barcodes and an optional epoxy layer. Keep a scannable code inside the tag’s safe area and clear of the strap slots.
A useful enrollment file separates the printed ticket number, the chip UID returned by the reader, and the event-system record. Add any encoded NFC content as its own field. The printed QR and RFID identifier can point to the same record without being the same value.
Synthetic planning only — not a production or platform import file. Use the example to agree field mapping and read-back checks with your event provider. Download synthetic handoff example · CSV ↓ Read field mapping & acceptance notes · TXT ↓
IC specifications from the chip manufacturers
These families appear in the supplier’s chip options. Their memory and authentication differ even when the wristband looks identical. The values below describe the IC, not a chip identified from a product photograph.
| Chip & interface | Memory & protection | Application fit |
|---|---|---|
| NTAG213 / NTAG215 / NTAG21613.56 MHz · ISO/IEC 14443 A · NFC Type 2 | 144 / 504 / 888 bytes user memory 32-bit password protection; manufacturer-programmed 7-byte UID | NDEF links and phone interactions. NDEF formatting also consumes memory. NXP Semiconductors datasheet ↗ |
| MIFARE Ultralight EV113.56 MHz · ISO/IEC 14443 A | 48 or 128 bytes user memory, depending on variant 32-bit password protection; three 24-bit counters | Ticketing workflows designed for the selected EV1 variant. Password protection is not the 3DES mechanism of Ultralight C. NXP Semiconductors datasheet ↗ |
| MIFARE Ultralight C13.56 MHz · ISO/IEC 14443 A | 144 bytes user data memory 3DES authentication | Existing systems using Ultralight C commands and keys. Its 192-byte total EEPROM is not 192 bytes of user data. NXP Semiconductors datasheet ↗ |
| EM4200LF · 125 kHz credential systems | Factory-programmed read-only identifier Identifier and encoding format selected for the LF reader | A listed LF option for compatible identification readers. It does not carry a writable NFC web link. EM Microelectronic datasheet ↗ |
Reader distance needs a finished-band test. The supplier’s event example lists 2–5 cm, with another WB505 listing giving a reader-dependent 2–10 cm range. Neither establishes a fixed distance for every chip or a long-range gate system. Check the selected antenna and chip while the band is worn.
Technical documents
The reference brings together published dimensions, artwork and closure options, chip memory and source links.
Download fabric wristband reference ↓PDF · reviewed 16 September 2026
Custom orders & samples
Choose a finish and closure, then add quantities, artwork, chip or reader details, event date and destination on the next page.
Sample charges, MOQ, pricing and schedule are stated for the selected assembly. Include the event platform’s required chip and data format when encoding is needed.
Sample ordering terms →For an event order, review the cost and delivery guide and reader, chip and platform approval plan before confirming your configuration.
The 350 mm measurement is the published flat strap length. Part of the strap forms the two tails passing through the slider, so it is not the usable wrist circumference. The selected lock, tag and tail allowance determine the closed fit. Use actual wrist measurements when choosing sizes.
No. Ultralight EV1 has 48 or 128 bytes of user memory, depending on the variant, and 32-bit password protection. Ultralight C has 144 bytes of user data memory and 3DES authentication. They share the 13.56 MHz ISO/IEC 14443 A interface, but the memory layout, commands and authentication workflow differ.
Yes, when the event system maps both identifiers to that record. Keep the printed ticket or QR value, chip UID and any encoded NFC content as separate fields in the enrollment file. For NTAG213/215/216, the UID is manufacturer-programmed; sequential ticket numbers are a separate field. QR plus NFC does not by itself create two-factor authentication.
No. The slider controls physical removal. Cashless use needs a compatible chip, readers, account software and the operator’s transaction rules. Specify the exact chip and personalization required by the selected platform; a wristband photo or matching frequency cannot establish platform compatibility.
May we use Google Analytics cookies to measure visits and inquiry actions? Your choice does not affect the contact form. Cookie details