ABOUT VEXELON
BUILT AFTER TOO MANY EMPTY CLAIMS.
VEXELON began in Chongqing with a rider who grew up around motorcycles and never stopped looking for a better line.
CHONGQING / RIDER-BUILT / ELECTRIC OFF-ROAD
One rider. Too many promises that did not hold up.
Growing up in Chongqing, motorcycles were never just a product category. They were how weekends, friendships, and the next challenge took shape.
When electric off-road motorcycles opened a new kind of ride, the interest was immediate. But the market asked riders to choose between premium machines that were out of reach for many and lower-cost options whose headline claims were difficult to trust.
After being let down by numbers that did not match the reality, the answer became simple: build the motorcycle he wanted to buy. VEXELON exists to make performance claims that are clear, honest, and tied to the conditions in which they are measured.
A rider's standard is built over time.
Every VEXELON decision traces back to a real frustration, a real ride, or a question that deserved a better answer.
Motorcycles were the first language.
Long before VEXELON, there were weekend rides, workshop conversations, and a habit of looking closely at how a machine responds.
ORIGIN / CHONGQING
Electric opened a new line through the dirt.
The quiet response and instant torque were exciting. The promise was obvious, but finding a machine with numbers worth trusting was not.
DISCOVERY / ELECTRIC OFF-ROAD
Build the bike we wanted to buy.
After too many claims failed to match reality, the answer was to make the testing, configuration, and compromises visible from the start.
STANDARD / NO EMPTY CLAIMS
A number is only useful when you can question it.
Tap a metric to see the kind of context we believe belongs next to a performance claim.
Power should be a real-world number.
Peak output is meaningful only when the system configuration and test conditions are clear. The figure is a reference point, not a promise that every ride will feel identical.
Ask for the configuration behind the claim.
Speed depends on more than a headline.
Rider weight, surface, temperature, battery state, gearing, and setup all affect speed. A useful claim should tell you what the test looked like.
Conditions are part of the specification.
The system is bigger than one component.
Voltage is one part of the platform. Controller settings, motor, battery capacity, thermal limits, and rider modes determine how the bike actually behaves.
The full configuration tells the honest story.
Performance you can look at twice.
Three principles keep the product honest from the first sketch to the first ride.
-
01
RIDER REALITY
Start with the terrain and the rider, then build the performance around what is actually useful.
-
02
CLEAR NUMBERS
Choose figures that riders can understand, question, and compare with the conditions behind them.
-
03
EARNED TRUST
No performance claim should be bigger than the testing and the build behind it.
Make the number mean something.
Power, range, speed, and weight are only useful when riders know how they were measured and which configuration they describe. Our standard is simple: state the conditions, call out the variables, and never use a bigger number just to win attention. Final specifications can vary by configuration; those differences should be visible.