Vantrue Endurance PRO 128GB: a card that claims almost nothing

Why a card with no numbers on it is worth testing

Most cards give you something to check. A printed 100 MB/s read, a 40 MB/s write, an endurance figure in hours with a bitrate condition in the fine print. This one gives you four class marks, a capacity, and a two-year warranty, and that is the entire list. Which makes it an unusually clean test: there is no marketing figure to beat or miss, so the bench is measuring the card rather than adjudicating a claim. It joins CKBench, the running index of every card on the bench, alongside the VIOFO High Endurance pair, which is the other dash cam brand selling an endurance card with no endurance rating on it, and the SanDisk MAX Endurance 128GB, which prints a full hours ladder and the bitrate that ladder assumes.

One unit, supplied by Vantrue, tested on September 10, 2026. Three full runs across two independent card readers, because the first run disagreed with the two that followed and I would rather show you that than quietly drop it. The same two-reader method cuts the other way too: on a used SanDisk High Endurance 512GB it pinned a multi-second write stall to the card, because the fault followed the card to the second reader instead of staying behind.

What the box claims, and what the card did

Everything below is read off the retail packaging and the card face, which agree with each other. Half of this table is empty on purpose: a claim the card does not make still gets a row, because the absence is information.

A2 is not a failure and I never score it as one. The A-classes assume command queuing that USB card readers do not perform, so A2 is untestable on any reader bench, for any card. The A1 thresholds of 1,500 read and 500 write IOPS are at least measurable at queue depth 1, and this card cleared both.

The word Endurance appears once, and never again

The card face reads Endurance PRO. The packaging never uses the word at all, and neither surface carries an endurance rating of any kind: no hours, no terabytes written, no bitrate condition to hang a figure on. That is not unique. The VIOFO High Endurance cards, all three capacities of them, do exactly the same thing, which is what turns it from one brand's quirk into a pattern worth naming. The contrast is SanDisk, whose High and MAX Endurance boxes both print a capacity-indexed hours ladder and the 26 Mbps Full HD condition that ladder assumes, so you can convert it into something real.

I cannot tell you why the rating is absent, and I am not going to guess. What I can tell you is what is printed, which is on the back of the pack in the two photos below, and that the model field on the applied label reads 128g. That is the capacity restated, not a part number, which means there is no SKU here to tell this hardware apart from a future revision of it.

How fast is it when the writing does not stop?

This is the number that decides a video speed class, and it is always the worst ten-second window rather than an average, because a camera does not get to record over the mean. Five minutes of continuous committed writing with the cooling fan off, sampled once a second.

Flat, and two grades above what it prints

Ten consecutive thirty-second blocks land between 84.1 and 84.4 MB/s. The worst single second in the whole five minutes is 77.6 MB/s. There is no cache cliff, and I checked that twice: the knee scan came back with no knee, and the whole-card fill later in this review held 82.4 MB/s across 126.4 GB without a single sample dropping below 60.

Against the V30 the card prints, 83.4 MB/s is 2.8 times the floor. It clears V60 as well, which is two grades above its own label. That is worth saying plainly and then putting in proportion: the one dash cam duty cycle I have actually measured, by reading a four-channel camera's own recordings off its bundled card, came to about 4.8 MB/s aggregate. This card's worst moment is roughly fourteen times that. For the job it is sold for, sustained write was never going to be the constraint, and the honest read is that it has enormous headroom rather than that it is unusually fast.

Does it slow down under the writes loop recording actually makes?

Loop recording is not one long clean write. It is scattered small writes: event saves, file table updates, overwrites of the oldest clip. Three passes of random 4K writes in a row shows whether a card's controller degrades as that churn accumulates. This is a directional indicator, not an endurance test, and nothing done in an hour tells you about year three.

It does not fade at all

983, 982, 983 write IOPS across three consecutive passes. The last pass sits 0.04% below the best one, which is noise rather than degradation. For comparison, the reference card in that panel is a cheap Class 4 unit that loses 71% of its write IOPS across the same three passes, and that collapse is what this test exists to find.

The settle behavior says the same thing from another angle. The bench writes an untimed warm-up pass before the timed one so the measured window starts on a controller that has finished reacting to the previous test. On both clean runs this card came out of the random 4K leg already writing at its full media rate, around 84 MB/s, on the first two thirty-second windows. It does not need to recover, because the churn did not cost it anything.

Is all the space really there?

Every free byte gets filled with data generated from a seeded random stream, then every byte gets read back and compared. It is slow and it is the only test that catches a fake, because a fraudulent card looks perfectly normal until you use the far end of it.

126.4 GB, verified, zero errors

126,415,273,984 bytes written across 118 files, the same number read back and compared, zero mismatched bytes and zero read errors. The card reported itself full exactly when it should have. That is a pass, and after three counterfeit 128GB cards earlier this month that returned 66, 48 and 65 GB of real space, it is not a formality.

The 98.8% is not a shortfall you should hold against it. Every card reserves flash for spares and metadata, no usable-capacity figure is printed on this package for it to miss, and genuine cards on this bench land between about 96.7% and 100.1% of their label. Throughput across the address range was flat too: 82.9, 82.9 and 81.6 MB/s writing across the first, middle and last tenth of the card, a spread of 1.5%. Tiered fake flash shows its seams there, and this card has none.

How hot does it get, and does it slow down?

Five minutes of uncooled sustained writing, with the temperature read at the reader's slot aperture the moment the timed write stops. The question is always two questions: how hot, and did the card give up any speed getting there.

The one place this card is behind its peers

It did not throttle. The write trace is flat at 84.2 MB/s for the full five minutes with no decay at the end, and the 126.4 GB fill held its speed too. On the test that matters most, heat cost this card nothing.

But 170 °F (76.7 °C) is the highest peak I have recorded from any 128GB card on this bench, and it got there while delivering mid-pack throughput rather than class-leading throughput. On heat per MB/s of work done it ranks ninth of the twenty 128GB cards on file. Two things make that worth a paragraph rather than a footnote. First, that reading is a floor, not a ceiling: it is taken at the slot aperture, and when I ejected cards and shot them face-on the aperture was under-reporting the card surface by 10 to 14 °F, which puts true surface in the low 80s °C against the roughly 85 °C these parts are typically rated for.

Second, and this is the part that matters for this specific product: my ambient was 76 °F in a climate-controlled room, and a windshield in summer is not 76 °F. This is a card sold to sit behind glass in a parked car. It produced the highest peak of anything in its capacity class while doing ordinary work in ideal conditions, which means it has the least margin in hand of any card here for the day the ambient climbs. It cost no speed on my bench and I am not calling it a defect. It is the one dimension where this card is measurably behind its peers, and it is behind them in exactly the environment it was built for.

One honest gap: all three runs independently returned 170 °F, which is good corroboration of the number, but there is no infrared frame on file for this unit. A thermal photo only means something if it is captured within seconds of the write stopping, and a card cools too fast for a later picture to be worth anything.

Why this review has three runs instead of one

The first run on this card, on a sealed unit that had never been written to, produced a sequential write that fell across three passes and a worst ten seconds of 20.3 MB/s, which would have published as V10. Two later runs, one on a second card reader and one back on the first, both returned 83.4 MB/s and V60. They agree with each other to the hundredth of a MB/s.

So the first run is excluded from every speed and class figure above, and I want to be straight about what I do and do not know. It is not the reader, because the third run used the same reader and came back clean. It is not sensitivity to the random-write churn that runs before the sustained test, because the third run did that churn too and still settled at full speed. And it is not something this bench does to fresh cards generally, because most cards here reproduce their own figures run to run. What is left is that it was the only run that started on a card which had never been written to, and that is suggestive rather than proof. A one-off event on my test machine cannot be ruled out either. I could not determine whether the cause was the card or my own bench, so I am not attributing it to the product, and it changes none of the numbers in this review. Update, 15 September 2026: the VIOFO High Endurance 32GB, built on the same Longsys platform, turned out to have done the same thing on its own first run in July and never again across five later runs on two readers, which makes a slow first-writes phase on this platform the more economical reading. My bench machine has also had background processes found and removed since, so a host event still cannot be excluded, and I am leaving the sentence above as written.

The capacity result above does come from that first run, because it is the only run that filled the card. That leg was flawless: not one of its 1,530 fill samples fell below 60 MB/s, and the whole-card read-back held 93.4 MB/s. Whatever the first few minutes were, it was long over before the fill began.

How the 4.5 breaks down

The bottom line

Judged on what it does rather than what it says, this is a good dash cam card. It beats the video class printed on it by a factor of 2.8, it does not fade under churn, its capacity is entirely real, and its write curve is one of the flattest I have recorded. If you already own one, or one arrives with your camera, there is nothing here that should worry you.

Judged on what it tells you, it is frustrating. There is no speed figure to compare against the card next to it on the shelf, and there is no endurance rating behind a card that puts the word Endurance on its face. Those are not test failures, they are documentation choices, and my rubric has no dimension for them, which is why they cost it nothing in the score and get a section of their own instead. The heat is the one measured mark against it, and it lands squarely in the use case the card was built for.

Disclosure: Vantrue supplied this card as part of a review kit for one of their dash cams. I did not buy it, and it was not inside the camera's retail box. Vantrue had no editorial input, 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.