Speederlash 128GB: a better card than its box says
A no-name microSD card from an Amazon seller with a Gmail support address, in a pack that gets its own card’s speed grade wrong. I bought it sealed, filled every byte, ran it on two readers and read its identity registers on a Raspberry Pi. The card turned out more honest than its box, and apart from the serial, the build date and one flag its registers are another brand’s.
No video for this bench run
Everything on this page came off the bench, not a camera. The channel covers the dash cams, phones and readers these cards end up in; subscribe and the next one lands in your feed the day it goes up.
The short version
The Speederlash 128GB is an honest V30 card sold in a box that undersells it. The pack prints U1; the card itself prints U3 and holds it, with its worst ten seconds of continuous writing at 44.25 MB/s on my primary reader and 43.94 on the second, after the whole card had been written once. It prints no speed figure at all. It read 96.8 MB/s, the ceiling of the standard UHS-I mode, and wrote 46.8 MB/s committed, and under that steady average it writes in a rhythm about three and a half seconds long: about 146 MiB at about 80 MB/s, then about 6 MB/s for a second and a half, over and over, for the whole card. Every one of its 125.1 GB came back byte for byte, and it peaked at 132 °F. My rating: 4/5, scored against the CKBench rubric.
Verdict: 4/5, an honest V30 card in a box that gets its specs wrongWho this card is for
- YesDash cams, security cameras and action camsIts worst ten seconds were 44.25 MB/s, about seven times what a 4K dash cam writes at 6 MB/s. It held V30 across a write of the whole card, and it was no slower after being filled.
- YesAnything that asks for V30 or U3It held both on two readers, fresh and after a whole-card write, which is more than its own box promises.
- NoCameras that ask for V60It never came near it: its steady write is 47 MB/s, and V60 needs 60 for every ten seconds.
- NoFast offloads, or apps run from the cardIts reads stop at 96.9 MB/s, the UHS-I SDR104 ceiling, and at queue depth one its random writes fell short of the A1 floor on my primary reader, 467 IOPS against 500, though they met it on the second.
125.1 GB of usable space is roughly 5 hours 47 minutes of single-channel 4K at 6 MB/s, or about 11 hours 35 minutes of 1080p60 at 3 MB/s, before a dash cam loop starts overwriting. Work out your own numbers in the dash cam storage calculator.
What is the Speederlash 128GB?
Speederlash is a name I found only on marketplace listings. No brand website turned up, the pack names no company, only an address in Pinghu Street, Longgang District, Shenzhen and Made in China, and after-sales support is a Gmail address. The card comes in a retail blister with an SD adapter, and neither the pack nor the card states a speed; the Amazon listing does. I bought this one sealed on Amazon on 6 October 2026, and it is the first Speederlash card on my bench.
It is worth testing for the same reason it is easy to dismiss. Plenty of no-name cards are fakes, and this one ticks the boxes that make me suspicious before I open it: a brand with no footprint, a pack with odd English, and fine print that contradicts itself. A fake would show up in the capacity test, and an inflated speed grade in the sustained write. The card is in CKBench now, the running index of every card on my bench, next to other budget 128 GB cards I have bought this autumn, among them the PNY Premier-X, the Silicon Power Superior Pro and the LinkMore XV23 Lite.
Every write figure on this page is a committed write: the data is on the flash before the clock stops, with no operating-system cache in the way. That is why the numbers here read lower than a marketing sheet or a quick benchmark; the methodology page explains the difference and why it is the one that matters for recording.
What the Speederlash 128GB claims, and what it did
| Claim | Printed | Measured | Verdict |
|---|---|---|---|
| Capacity | 128 GB (sticker on the pack front, card face); the pack defines 1GB as “1,000,000 bytes” | 125.1 GB written and verified, zero errors; the card declares 97.71% of its label | VERIFIED |
| Read speed | None on the pack or the card (the Amazon listing says up to 95 MB/s) | 96.8 MB/s (ProGrade PGM0.5); 96.9 MB/s (SanDisk QuickFlow SDDR-B751). Both at the SDR104 ceiling | NOT CLAIMED |
| Write speed | None anywhere | 46.8 MB/s committed (ProGrade); 47.0 MB/s (QuickFlow) | NOT CLAIMED |
| Speed class | C10 (card face only) | 44.25 MB/s worst ten seconds, far above C10’s 10 | HELD |
| UHS speed grade | U3 on the card face; U1 on the pack back | 44.25 MB/s worst ten seconds (ProGrade, first run); 43.94 (QuickFlow, after a whole-card write), above U3’s 30 | HELD (U3) |
| Video speed class | V30 (card face, pack back) | 44.25 and 43.94 MB/s worst ten seconds; 40.37 across a write of the whole card | HELD |
| App performance class | A1 (card face only) | 1,523 read / 467 write IOPS at queue depth one on the ProGrade, under A1’s 500 write floor; 1,864 / 519 on the QuickFlow, over it. Indicative only: the SD A-class procedure differs | NOT TESTABLE |
| Bus | UHS-I (card face, pack back) | One row of eight contacts; declares SD specification 6.x; reads at the SDR104 ceiling on two readers | CONSISTENT |
| Waterproof, shock, temperature and X-ray resistant | One line on the pack back, with no test conditions | n/a | NOT TESTABLE |
| Endurance rating | None printed | n/a | NOT CLAIMED |
| Operating temperature | 0 °C to 70 °C (pack back) | 132 °F (55.6 °C) at its hottest after five minutes of uncooled writing in a 76 °F room; 14.4 °C under the printed maximum | NOT A PERFORMANCE CLAIM |
| Warranty term | None on the pack (the Amazon listing says a 5-year limited warranty) | n/a | NOT A PERFORMANCE CLAIM |
The card prints class marks and nothing else, so the class marks are what it is judged on, and it holds every one of them with room. The read figure exists only on the Amazon listing, which says up to 95 MB/s. My rubric scores a speed only when the card, its pack or the maker’s own published spec states it, and a retailer listing does not count; the card would meet it anyway, at 96.8 MB/s on the ProGrade and 96.9 on the QuickFlow, the practical ceiling of the SDR104 mode, where most standard UHS-I cards on my bench land. A1 is not testable on a USB reader either: at queue depth one the card cleared both A1 floors on the QuickFlow and fell just short of the write floor on the ProGrade, which is indicative and nothing more.
A box that gets its own card wrong
The front of the blister carries the brand, a holographic 128GB sticker, three lines of feature copy (Data transformation security, presumably meaning transfer, Strong compatibility and reliability and 4K Ultra HD video quality) and the card itself under the plastic beside its adapter. There is no speed figure anywhere on it. The back adds icons for video, photos and audio, a durability line, the SD trademark notice, an address in Shenzhen with no company name, an operating range of 0 to 70 °C and one set of class marks. Amazon’s fulfilment sticker covers the end of the address line. There was no returns sticker on any panel.
Those class marks are where the box and the card part ways. The pack prints V30 beside a U1, the lowest UHS speed grade, with a 10 MB/s floor. The card under the plastic prints V30 beside a U3, whose floor is 30 MB/s, plus Class 10 and A1, neither of which appears on the pack. V30 with U1 is an odd pair in any case: V30 promises the same 30 MB/s sustained write that U3 does, so a card that earns V30 earns U3 as well. The card’s own registers, which I read before its first run, declare U3, and so does the Amazon listing. The pack is the odd one out, and it errs in the card’s favour: the card holds U3, as the sustained write below shows. The capacity footnote has a slip of its own. It defines 1GB as 1,000,000 bytes, short by a factor of a thousand; a gigabyte on a memory card label is 1,000,000,000 bytes, and that is the definition the card is measured against below.
The card arrived empty, formatted exFAT with 128 KiB clusters and no volume label. One detail of that factory format is unusual on my bench: its partition starts 32 KiB into the card, where every other card whose factory format I have recorded starts its partition on a 1, 4 or 16 MiB boundary. It suggests a different factory tool from the other cards’. I ran the card as it came, so the results below include whatever that costs.
Five minutes at 47 MB/s, three and a half seconds at a time
The timed write starts after an untimed warm-up that runs until the speed stops changing, so the five minutes that decide the video class start on a settled card. On this card the warm-up settled at the earliest point the tool can declare, 60 seconds, at 46.1 MB/s. The trace below is the scored run, one sample a second, with the speed-class floors marked. The first thirty seconds averaged 46.3 MB/s and the last thirty 47.1, the whole five minutes 47.0, and the worst ten seconds were 44.25 MB/s, at 1:27. On the second reader, after the whole card had been written once, the same five minutes read 46.9 steady with worst ten seconds of 43.94.
Speederlash 128GB
44.25 is 14.25 MB/s above the V30 floor, so V30 and U3 hold with room to spare. The trace is not a smooth line, though, and the jagged band is the card, not noise. It writes in a rhythm about three and a half seconds long: roughly 146 MiB goes in at about 80 MB/s, then the card writes at about 6 MB/s for a second and a half, and it repeats, 86 times in the five minutes and all the way through a write of the whole card. A one-second sample cannot draw a cycle that short cleanly, so the trace jumps between seconds as low as 5 MB/s and as high as 83; a fit to the samples gives a period of 3.46 seconds in the timed run and 3.54 through the fill, with the same 155 MiB of data in every cycle either way.
The slow part is not a stall. The longest any single 1 MiB write took was 240 milliseconds, and the bench flags anything over half a second. A camera buffers a few seconds of video and never sees the rhythm; what it sees is the average, about 47 MB/s, and the worst ten seconds, which this card measures honestly. They depend a little on where a window falls in the cycle, 40.2 MB/s for the worst nine seconds and 46.4 for the worst fourteen, and every one of them clears V30. Among the budget cards on my bench that puts it beside the PNY Premier-X (47.1) and the FitcamX (43.8), above the Silicon Power Superior Pro (37.8) and the Newegg TeamGroup (35.5), and well below the LinkMore XV23 Lite (77.3).
The Gigastone’s registers, one flag apart
Every SD card carries a set of registers, written at the factory, that a USB reader cannot show you and a native SD host can. One names the card: manufacturer ID, OEM ID, product name, revision, serial and build date. The others describe it: how big it is, which SD specification it follows, which speed classes it declares. I read this card’s on a Raspberry Pi before its first run, and apart from the serial, the build date and a single flag they are those of the Gigastone High Endurance Pro 128GB, a card from an established brand that I benched in September. The flag sits in the SD specification register and says whether erased memory reads back as zeros or as ones; there the Speederlash matches the Newegg TeamGroup 128GB to the byte instead.
| Field | Speederlash 128GB | Gigastone High Endurance Pro 128GB | PNY Premier-X 128GB |
|---|---|---|---|
| Manufacturer ID / OEM ID | 0xFE / “42” | 0xFE / “42” | 0x74 / 0x4A60 |
| Product name / revision | SD / 2.0 | SD / 2.0 | SD / 6.1 |
| Build date | May 2026 | November 2025 | February 2025 |
| Declared capacity (CSD) | 125,069,950,976 bytes on all three, the same register byte for byte | ||
| Declared classes (SD Status) | C10, U3, V30 and A1 on all three, the same 64 bytes | ||
| SD specification (SCR) | 6.x | 6.x, one flag different | 6.x, one flag different |
Manufacturer ID 0xFE is not on any public list, so it names no company; my manufacturer ID register has five cards under it now, two of them free cards bundled with dash cams. The SD Status block, the 64 bytes that declare the speed classes and a few performance fields, is identical on all five and on the PNY Premier-X, which reports a different manufacturer ID, and it carries a value of 4 in a performance field that no card off this platform reports. Whatever is inside these cards, it is one platform, and on my bench alone it is sold or bundled under six names, which the identity explainer lays out register by register.
That lets me compare how the platform’s cards behave, and they are not all the same card. Every one of them takes data at about 80 MB/s; what differs is what happens when that first stage fills.
| Card | Identity | Fast stage | Then drops to | Steady | Worst 10 s |
|---|---|---|---|---|---|
| FitcamX 64GB (bundled) | 0xFE / SZYL | about 80 MB/s | about 8 MB/s, 2.13 s cycle | 47.1 MB/s | 43.83 MB/s |
| Newegg TeamGroup 128GB | 0xFE / 42 / SD | about 80 MB/s | about 5 MB/s, 2.7 s cycle | 40.2 MB/s | 35.55 MB/s |
| Speederlash 128GB | 0xFE / 42 / SD | 81.0 MB/s | about 6 MB/s, 3.5 s cycle | 47.0 MB/s | 44.25 MB/s |
| PNY Premier-X 128GB | 0x74 / SD | 80.7 MB/s | about 3 MB/s, 4.2 s cycle | 54.9 MB/s | 47.40 MB/s |
| Botslab 128GB (bundled) | 0xFE / SZYL | 80 MB/s | about 52 MB/s, 9.5 s cycle | 58.5 to 59.1 MB/s | 51.3 to 53.9 MB/s |
| Gigastone High Endurance Pro 128GB | 0xFE / 42 / SD | 82 MB/s | about 52 MB/s, 9 s cycle | 61.3 MB/s fresh | 59.56 MB/s fresh |
The Speederlash carries the Gigastone’s identity and writes like the other end of the family: a short cycle that drops to about 6 MB/s, not the Gigastone’s nine-second saw-tooth with a 52 MB/s lower step. It sits between the TeamGroup and the PNY on the length of its cycle, the size of its fast stage, its average and its worst ten seconds. The registers name the platform; they do not tell you which build of it you are holding, or which flash is behind it. The LinkMore XV23 Lite taught the same lesson on another platform, and it is the reason I test every card rather than trusting a register match.
125.1 GB, every byte verified
The capacity test wrote 117 files of unpredictable, dedup-proof data until the card was full, 125,065,101,312 bytes, then read every one of them back and compared. Zero mismatched bytes. Zero read errors. The fill took 45 minutes 37 seconds and the read-back 22 minutes 19 seconds. Across the first, middle and last tenth of the card the write ran at 46.2, 45.9 and 45.9 MB/s, a spread of 0.76%, and the read spread by 0.94%: flat from one end of the card to the other, where the three no-brand fakes on my bench spread by 10 to 23%.
Every byte, written and read back
The three-and-a-half-second rhythm ran through the whole fill, at the same 155 MiB a cycle from the first gigabyte to the last, and the worst ten seconds anywhere in it were 40.37 MB/s, still V30. The chart below puts this fill beside the two other cards on my bench that declare exactly the same capacity, all three filled on the same reader on their first run.
Speederlash-128GB_2026-10-21_135703, PNY-Premier-X-128GB_2026-09-17_133234 and Gigastone-High-Endurance-Pro-128GB_2026-09-16_202449. All three verified every byte.The card declares 125,069,950,976 bytes, 97.71% of the 128 GB on the label, which is ordinary overhead for a genuine card and the same figure as the Gigastone and the PNY. Windows will show it as about 116 GB, because it counts in binary, and that is the figure the Amazon listing quotes as usable space. That is arithmetic, not a shortfall; the methodology page has the conversion. The capacity row of the rubric scores the declared share of the label, and 97.71% is a 4.
No slower after a whole-card write
Some cards write much more slowly once they have been filled, until something tells them which space is free again; why a used microSD card tests slower covers the effect. A card reader cannot send that signal, so a card filled and emptied over USB stays in that used state, and it is the state a dash cam card lives in. The Gigastone, which reports this card’s identity, showed it on my bench. So the Speederlash’s first run ended by filling and emptying the whole card, and its second run started 29 minutes later on the other reader.
| Measurement | Speederlash, first run | Speederlash, after the fill | Gigastone, first run | Gigastone, after the fill | PNY, first run | PNY, after the fill |
|---|---|---|---|---|---|---|
| Sequential write, committed | 46.8 MB/s | 47.0 MB/s | 60.6 MB/s | 58.5 MB/s | 53.6 MB/s | 53.8 MB/s |
| Worst ten seconds | 44.25 MB/s | 43.94 MB/s | 59.56 MB/s | 31.04 MB/s | 47.40 MB/s | 47.19 MB/s |
| Change in the worst ten seconds | −0.7% | −47.9% | −0.4% | |||
The Speederlash came back within a third of a megabyte a second of its first run, on a different reader, which is the kind of agreement two readers give on a card that has not changed. The Gigastone lost almost half its worst ten seconds after its first fill, on the same reader, and needed a native SD erase to recover; the Speederlash, like the PNY, has nothing to recover from.
Random writes barely move it
Loop recording is a long write interrupted constantly by small ones, and random 4K writes are the bench version of that: three twenty-second passes, and the question is whether the third is as fast as the first. On this card it nearly was. The scored run did 479, 458 and 465 write IOPS, 1.96, 1.88 and 1.90 MB/s, a fade of 3.06%, inside the 5% the bench itself treats as noise, and the card was back at 90% of its sustained rate within 12 seconds of continuous writing afterwards.
One minute of loop-recording abuse
This card: run Speederlash-128GB_2026-10-21_135703 · reference card: lab baseline, same bench, same test · cardcheck v0.8.5
The second reader’s run did 518, 524 and 517 write IOPS and read 22% faster at random than the ProGrade, 1,864 IOPS against 1,523. Random figures move with the reader on this bench, which is part of why the A classes cannot be tested on a USB reader, and the rubric scores the primary reader’s run, where this is a 5.
132 °F at its hottest, under its own 70 °C limit
This is one of the few cards on my bench that prints an operating range, 0 to 70 °C, and the rubric holds it to that maximum rather than the 85 °C it assumes for a card that prints none. At the end of five minutes of uncooled writing in a 76 °F room the card read 131 °F on the primary reader, and the thermal frame taken in the last seconds of that write reads 131.0 °F at its hottest point. On the second reader it read 132 °F. The rubric takes the highest reading on file: 132 °F is 55.6 °C, 14.4 °C under the printed 70, which scores a 3.5.
It got warm. It did not slow down.
The second reader’s run read 132 °F at 76 °F ambient, the scored peak · Run Speederlash-128GB_2026-10-21_135703 · cardcheck v0.8.5 · ProGrade PGM0.5
It did not throttle: the last thirty seconds of the timed write ran at 47.1 MB/s against 46.3 for the first thirty. 132 °F is a cool reading by the standards of my bench, mostly because the card writes slowly, and heat follows work. The row’s 3.5 is the price of printing a range at all: had the pack printed nothing, the rubric would have assumed 85 °C and the same 132 °F would have scored a 5. I would rather a card printed its real limit. 14.4 °C of margin in a 76 °F room is comfortable for a dash cam; a windshield in summer is hotter than a reader with its fan off, so it is a reason not to bury this card in a camera that already runs warm, not a reason to avoid it.
Two readers, one answer
Every card I review runs on my primary reader, a ProGrade PGM0.5, and again on a SanDisk QuickFlow SDDR-B751, which can drive a faster bus mode on cards that support one. This card ran once on each, the ProGrade run first and with the whole-card fill.
| Measurement | ProGrade PGM0.5 (primary) | QuickFlow SDDR-B751 |
|---|---|---|
| Card at the start of the run | sealed, first run | after a whole-card write |
| Sequential read | 96.8 MB/s | 96.9 MB/s |
| Sequential write, committed | 46.8 MB/s | 47.0 MB/s |
| Sustained write, steady state | 47.0 MB/s | 46.9 MB/s |
| Sustained write, worst ten seconds | 44.25 MB/s | 43.94 MB/s |
| Write cycle | 3.46 s | 3.47 s |
| Random 4K read / write | 1,523 / 467 IOPS | 1,864 / 519 IOPS |
| Peak temperature | 131.0 °F (frame) | 132 °F |
| Longest single write | 240 ms | 273 ms |
The two readers agree to within 1% on every write figure, so the card, not the reader, sets its speed, and the QuickFlow found no faster bus mode to use: the card reads at the SDR104 ceiling on both. Random reads run higher on the QuickFlow on every card I have run on both readers, so that part is normal.
How the 4 breaks down
Speederlash microSDXC 128GB
Scored against the CKBench rubric. Five dimensions, each out of 5, every row read off its published table.
Final score: 4 out of 5. The five dimensions average 4.1. An honest card that holds every class mark it prints, U3 included, through a write of the whole card and after it, and verifies every byte, giving points back for a lower-V30 sustained write, an ordinary 97.71% of its label and the 70 °C limit it prints and stays 14.4 °C under.
Both readers give the same rows: the lowest class claim is a 5 at 146.5% or 147.5%, and the worst ten seconds are a 3 at 43.94 or 44.25.
Frequently Asked Questions
Is the Speederlash 128GB a good microSD card?
Yes, for what it is. It holds every class mark printed on the card, C10, U3 and V30, with its worst ten seconds of continuous writing at 44.25 MB/s on my primary reader and 43.94 on the second, after a write of the whole card. It read 96.8 MB/s and wrote 46.8 MB/s committed, verified every one of its 125.1 GB with zero errors and peaked at 132 °F. It is a lower-V30 card, not a fast one, and it scores 4 out of 5.
Is the Speederlash 128GB U3 or U1?
U3. The card face prints U3, its registers declare U3 and the Amazon listing says U3; only the back of the retail pack prints U1. On my bench it held U3’s 30 MB/s floor with 44.25 MB/s through its worst ten seconds on a ProGrade reader and 43.94 on a SanDisk QuickFlow, and it held V30, which needs the same 30 MB/s.
Is the Speederlash 128GB really 128GB?
Yes. I filled every free byte with unpredictable data and read it all back: 125,065,101,312 bytes written and verified, zero mismatched bytes, zero read errors. The card declares 125,069,950,976 bytes, 97.71% of the 128 GB label, which is ordinary overhead for a genuine card. Windows shows it as about 116 GB because Windows counts in binary, and that is the usable figure the Amazon listing gives.
Is the Speederlash 128GB good for a dash cam?
Yes. Its worst ten seconds of committed writing were 44.25 MB/s, about seven times what a 4K dash cam writes, and it held V30 across a write of the whole card and was no slower after being filled, which is what loop recording does to a card. It peaked at 132 °F in a 76 °F room with no throttling, 14.4 °C under its printed 70 °C limit. Its 125.1 GB holds about 5 hours 47 minutes of 4K at 6 MB/s.
Why does the Speederlash 128GB write speed jump around?
It writes in a rhythm about three and a half seconds long: roughly 146 MiB at about 80 MB/s, then about 6 MB/s for a second and a half, repeating for the whole card. A one-second sample draws that as a jagged trace between about 5 and 83 MB/s. The average is about 47 MB/s and the worst ten seconds 44.25, which is what a camera with even a small buffer sees. The longest single 1 MiB write took under 300 milliseconds, so the slow part is slow writing, not a stall.
Who makes Speederlash microSD cards?
The pack does not say. It gives an address in Pinghu Street, Longgang District, Shenzhen, says Made in China and lists a Gmail address for after-sales support, and I found no Speederlash website. The card’s identity registers report manufacturer ID 0xFE, which no public list assigns, with the product name SD: the same identity as the Gigastone High Endurance Pro 128GB, so they name a platform, not a maker.
Is the Speederlash 128GB the same card as the Gigastone High Endurance Pro?
Not in the way it writes. Apart from the serial and the build date, both report the same identity, the same declared capacity to the byte and the same 64-byte SD Status. But the Gigastone writes on a nine-second cycle that averages about 61 MB/s fresh, and its worst ten seconds fell from 59.6 to 31.0 after its first whole-card write; the Speederlash writes on a three-and-a-half-second cycle that averages about 47 and was no slower after its fill. The Gigastone review covers that card.
The bottom line
The Speederlash 128GB is a better card than its box says. The pack prints U1 and gets its own capacity footnote wrong; the card prints U3, declares U3 in its registers and holds U3, and V30, through a write of the whole card and after it. It verifies every byte of an ordinary 97.71% of its label, runs cool, and stays inside the 70 °C its pack prints. It is not fast: about 47 MB/s, written in a three-and-a-half-second rhythm a camera never notices, with reads at the standard UHS-I ceiling. For a dash cam, a security camera or an action cam recording at V30 rates it does the job; for anything that wants V60, or quick offloads on a premium reader, look higher.
It is also another reminder that the identity a card reports belongs to a platform, not a product. This card reports the Gigastone High Endurance Pro’s identity, capacity and declared classes to the byte and writes nothing like it, and it shares the PNY Premier-X’s capacity register while sitting between the PNY and the Newegg TeamGroup on the length of its write cycle, its average and its worst ten seconds. Only the bench says which card you are holding. And a no-name brand with a Gmail address is not the same thing as a fake: this one is honest where it matters, in the capacity test and the class marks, and only its box is careless.
Sample size: one unit, purchased sealed at retail from Amazon on 6 October 2026. Two runs on two readers on 21 October 2026 under CKBench protocol v1.27.
Device identity: what this card reports about itselfFor anyone checking their own card or tracking silent hardware revisions
| Raw CID register | fe3432534400000020…01a500 (serial digits elided) |
| Manufacturer ID (MID) | 0xFE, on no public list; five cards on my bench report it, and the Gigastone High Endurance Pro 128GB and Newegg TeamGroup 128GB report this card’s whole identity string |
| OEM / application ID (OID) | 0x3432, “42” |
| Product name (PNM) | SD, a generic name |
| Product revision (PRV) | 2.0 |
| Serial number (PSN) | Per unit, withheld; on this platform it is a small counter value |
| Manufacture date (MDT) | 05/2026 |
| Declared capacity (from CSD) | 244,277,248 sectors of 512 bytes = 125,069,950,976 bytes, 97.71% of the label |
| SD specification (from SCR) | SD_SPEC 2 with SD_SPEC3 = 1, SD_SPEC4 = 1 and SD_SPECX = 2 (specification 6.x), so the UHS-I and U3 marks are legitimately declared |
| Declared classes (from SD Status) | Class 10, U3, V30 and A1, matching the card face, not the pack’s U1 |
| Card back | A single row of eight contacts; no markings |
| Factory format | exFAT, 128 KiB clusters, no volume label, no user files, the partition starting 32 KiB into the card |
| Captured on | Raspberry Pi 4 native SD host, no USB bridge in the path · 2026-10-21 |
The MID, OEM ID, product name and revision are model-level, but on this card they are shared with at least two other brands’ products, so a match tells you the platform, not the card. The serial and the manufacture date are per unit. The card back carries no lot or date marks to check the build date against.
Disclosure: I bought this card at retail from Amazon on 6 October 2026. Speederlash had no involvement in or knowledge of this review, saw no result before publication, and had no opportunity to influence any number on this page. This post contains affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you. Affiliate links like these and my YouTube channel are what keep the site running.