Lexar
Lexar THOR Z RGB DDR5-6000 Spec and Price in Brazil
DDR52x16GBUDIMM12.67 ns true latency
Released January 8, 2026
Released in January 2026, this 32GB RGB kit runs 6000 MT/s at CL38-48-48-96 and 1.35V — the flashier-sounding of Lexar's two DDR5 kits here, but actually the looser-timed one. THOR Z reads as a gaming-aesthetic pick more than a latency-tuned part, especially next to Lexar's own ARES kit. Good for builders prioritizing the RGB look on a modern DDR5 platform.
Tied 40th of 139 models in the RAM catalog on Speed — 33 models share this figure.
Current best price
No tracked price — this page compares specifications alone.
Specifications
- Capacity
- 2x16GB
- True latency
- 12.67 ns
- Memory type
- DDR5
- Speed
- 6000 MT/s
- CAS latency
- Form factor
- UDIMM
- Voltage
- 1.35 V
- Timings
- 38-48-48-96
- Modules
- 2
- RGB
- Yes
Capacities
| Configuration | Part number | Speed | CAS latency | True latency |
|---|---|---|---|---|
| 2x16GB | — | 6000 MT/s | 38 | 12.67 ns |
| 2x16GB CL36 | — | 6000 MT/s | 36 | 12.00 ns |
| 2x16GB CL32 | LD5U16G60C32LG-RUD | 6000 MT/s | 32 | 10.67 ns |
| 2x16GB CL28 | — | 6000 MT/s | 28 | 9.33 ns |
| 2x16GB 6800 CL34 | LD5U16G68C34LA-RGD | 6800 MT/s | 34 | 10.00 ns |
| 2x16GB 8000 CL38 | — | 8000 MT/s | 38 | 9.50 ns |
Guides for this category
How much RAM you actually needHow to size memory from the pressure your machine is under now, why running short quietly costs speed, and when a matched pair beats one stick.RAM speed and latency, and when they matterWhat a kit's MT/s and CAS latency each measure, why true latency is the two together, and the machines where the numbers actually change anything.SO-DIMM vs DIMM: the memory a laptop takesWhy laptop memory is a different module from desktop memory, how DDR4 and DDR5 are keyed apart, and why some machines take no module at all.What is ECC memory, and when you need itWhat error-correcting memory actually catches, how registered and load-reduced modules differ from unbuffered ones, and why the platform decides.
Sources
Every spec above was pulled from one of these — a field a source didn't state was left off rather than estimated.