TEAMGROUP is a Taiwanese manufacturer, founded in 1997, that makes a range of memory products — including RAM, SSDs, thumb drives, SD cards, and — of course — microSD cards. They also sell some PC accessories such as cases, fans, and CPU coolers.
Their products seem to come up fairly frequently in my Amazon searches. An anonymous donor sent me a set of the TEAMGROUP High Endurance 64GB’s, which caused me to ponder about what else they had.
This one made me thing of the Kingston Canvas Go! Plus — what with having “GO” as part of the name — which made me think that this was TEAMGROUP’s high-performance option. Looking at what they have available, it looks like that wasn’t the case — they have a few options that advertise better speeds — but this one boasted 100 MB/sec read speeds and 90 MB/sec write speeds — which would be impressive if it managed to pull them off.
It did not, in fact, pull them off.
It did, however, score in the bottom half of all cards I’ve tested so far for performance — except for sequential write speeds:
| Measurement | Percentile Score* |
|---|---|
| Sequential Read | 48th |
| Sequential Write | 66th |
| Random Read | 48th |
| Random Write | 45th |
* As of June 2nd, 2026. If you’re not familiar with percentile scores, think of them as “this card did better than X% of all cards I’ve tested”.
This card bears the U3, V30, and A1 performance marks. On average, the results I got were good enough to qualify for the U3 and V30 marks, but not the A1 performance mark. (The A1 performance mark requires random read speeds of at least 1,500 IOPS/sec and random write speeds of at least 500 IOPS/sec — and none of the three samples were able to hit 500 IOPS/sec in random write speeds. However, I’ll throw out my standard disclaimer: my testing methods do not align with those prescribed by the SD Physical Layer specification; it’s possible that they would have done better had they been tested under proper conditions.)
On the endurance testing front:
- Sample #1 has survived 2,486 read/write cycles in total so far; although as of this writing, it’s stuck in a neverending loop of I/O errors.
- Sample #2 has not yet hit the 2,000 read/write cycle mark; it is currently expected to get there sometime in June 2026.
- Sample #3 has not yet hit the 2,000 read/write cycle mark; it is currently expected to get there sometime in June 2026.
June 2, 2026