TMR sticks
Gamepad Leadjoy Saber Plus

Leadjoy Saber Plus

Top contributors
Danny89plusminuseqGarret's Storiesabhijit deolГеймпад Бар
Test Status:User Verification (22 June 2026)
LatScore : Wired A+, Wireless A
Compatible: LinuxSwitchWindows
Interfaces: CableDongleBluetooth
Price: $59.99

Leadjoy Saber Plus Input lag comparison

#ConnectionMode
LatencyAverage (ms)
Polling RateMedian (Hz)
Jitter
OSBuild ver.
FWTester ver.
Latency P82
1
Cable PRIMARYXInput
🔘2.95
🕹️2.89
962.46
🔘0.44
🕹️0.49
Win 11
10.0.26200
33.15.12
5.3.0.0
plusminuseq
🔘
Button LatencyP82
✓ Selected
1.82 ms
2.95 ms
3.9 ms
0.44 ms
962.46 Hz (see 📊)
#9176 • 2026-06-22
Prometheus 82 v5.3.0.0
Win 11 Build 10.0.26200
plusminuseq
Cable • XInput
33.15.12
🕹️
Stick LatencyP82
✓ Selected
1.48 ms
2.89 ms
4.11 ms
0.49 ms
962.46 Hz (see 📊)
#9171 • 2026-06-22
Prometheus 82 v5.3.0.0
Win 11 Build 10.0.26200
plusminuseq
Cable • XInput
33.15.12
📊
Polling Rate
0.91 ms
1.04 ms
4.09 ms
0.69 ms
962.46 Hz
669.51 Hz
#9168 • 2026-06-22
Polling v2.0.2.5
Win 11 Build 10.0.26200
plusminuseq
Cable • XInput
33.15.12
Note: This test are based on polling rate and do not represent actual input-lag.
2
CableSony
🔘2.44
🕹️2.64
998
🔘0.38
🕹️0.48
Win 11
10.0.26200
36.16.12
5.3.0.2
Danny89
🔘
Button LatencyP82
1.7 ms
2.44 ms
3.25 ms
0.38 ms
998 Hz (see 📊)
#9437 • 2026-06-27
Prometheus 82 v5.3.0.2
Win 11 Build 10.0.26200
Danny89
Cable • Sony
36.16.12
🕹️
Stick LatencyP82
1.7 ms
2.64 ms
3.71 ms
0.48 ms
998 Hz (see 📊)
#9436 • 2026-06-27
Prometheus 82 v5.3.0.2
Win 11 Build 10.0.26200
Danny89
Cable • Sony
36.16.12
📊
Polling Rate
0.98 ms
1 ms
2.02 ms
0.28 ms
998 Hz
999.95 Hz
#9438 • 2026-06-27
Polling v2.0.2.6
Win 11 Build 10.0.26200
Danny89
Cable • Sony
36.16.12
Note: This test are based on polling rate and do not represent actual input-lag.
3
CableSwitch
🔘3.81
🕹️3.83
250
🔘1.12
🕹️1.13
Win 11
10.0.26200
36.16.12
5.3.0.2
Danny89
🔘
Button LatencyP82
1.7 ms
3.81 ms
5.95 ms
1.12 ms
250 Hz (see 📊)
#9440 • 2026-06-27
Prometheus 82 v5.3.0.2
Win 11 Build 10.0.26200
Danny89
Cable • Switch
36.16.12
🕹️
Stick LatencyP82
1.73 ms
3.83 ms
5.95 ms
1.13 ms
250 Hz (see 📊)
#9439 • 2026-06-27
Prometheus 82 v5.3.0.2
Win 11 Build 10.0.26200
Danny89
Cable • Switch
36.16.12
📊
Polling Rate
3.98 ms
4 ms
5 ms
0.06 ms
250 Hz
250.47 Hz
#9441 • 2026-06-27
Polling v2.0.2.6
Win 11 Build 10.0.26200
Danny89
Cable • Switch
36.16.12
Note: This test are based on polling rate and do not represent actual input-lag.
4
Dongle PRIMARYXInput
🔘5.59
🕹️6.71
984.25
🔘0.70
🕹️0.71
Win 11
10.0.26200
33.15.12
5.3.0.0
plusminuseq
🔘
Button LatencyP82
✓ Selected
4.07 ms
5.59 ms
7.38 ms
0.7 ms
984.25 Hz (see 📊)
#9175 • 2026-06-22
Prometheus 82 v5.3.0.0
Win 11 Build 10.0.26200
plusminuseq
Dongle • XInput
33.15.12
🕹️
Stick LatencyP82
✓ Selected
5.11 ms
6.71 ms
8.28 ms
0.71 ms
984.25 Hz (see 📊)
#9172 • 2026-06-22
Prometheus 82 v5.3.0.0
Win 11 Build 10.0.26200
plusminuseq
Dongle • XInput
33.15.12
📊
Polling Rate
0.9 ms
1.02 ms
4.02 ms
0.59 ms
984.25 Hz
866.53 Hz
#9169 • 2026-06-22
Polling v2.0.2.5
Win 11 Build 10.0.26200
plusminuseq
Dongle • XInput
33.15.12
Note: This test are based on polling rate and do not represent actual input-lag.
5
DongleSony
🔘5.36
🕹️6.24
996.02
🔘0.70
🕹️0.65
Win 11
10.0.26200
36.16.12
5.3.0.2
Danny89
🔘
Button LatencyP82
3.93 ms
5.36 ms
7.27 ms
0.7 ms
996.02 Hz (see 📊)
#9455 • 2026-06-27
Prometheus 82 v5.3.0.2
Win 11 Build 10.0.26200
Danny89
Dongle • Sony
36.16.12
🕹️
Stick LatencyP82
4.9 ms
6.24 ms
7.88 ms
0.65 ms
996.02 Hz (see 📊)
#9454 • 2026-06-27
Prometheus 82 v5.3.0.2
Win 11 Build 10.0.26200
Danny89
Dongle • Sony
36.16.12
📊
Polling Rate
0.98 ms
1 ms
3.01 ms
0.4 ms
996.02 Hz
999.91 Hz
#9456 • 2026-06-27
Polling v2.0.2.6
Win 11 Build 10.0.26200
Danny89
Dongle • Sony
36.16.12
Note: This test are based on polling rate and do not represent actual input-lag.
6
DongleSwitch
🔘8.51
🕹️8.86
125
🔘2.27
🕹️2.25
Win 11
10.0.26200
36.16.12
5.3.0.2
Danny89
🔘
Button LatencyP82
4.27 ms
8.51 ms
12.47 ms
2.27 ms
125 Hz (see 📊)
#9458 • 2026-06-27
Prometheus 82 v5.3.0.2
Win 11 Build 10.0.26200
Danny89
Dongle • Switch
36.16.12
🕹️
Stick LatencyP82
4.88 ms
8.86 ms
13.21 ms
2.25 ms
125 Hz (see 📊)
#9457 • 2026-06-27
Prometheus 82 v5.3.0.2
Win 11 Build 10.0.26200
Danny89
Dongle • Switch
36.16.12
📊
Polling Rate
0 ms
8 ms
9.01 ms
1.14 ms
125 Hz
129.42 Hz
#9459 • 2026-06-27
Polling v2.0.2.6
Win 11 Build 10.0.26200
Danny89
Dongle • Switch
36.16.12
Note: This test are based on polling rate and do not represent actual input-lag.
7
Bluetooth PRIMARYXInput
🔘16.3
🕹️17.1
67.52
🔘6.05
🕹️5.77
Win 11
10.0.26200
33.15.12
5.3.0.0
plusminuseq
🔘
Button LatencyP82
✓ Selected
5.05 ms
16.27 ms
34.39 ms
6.05 ms
67.52 Hz (see 📊)
#9174 • 2026-06-22
Prometheus 82 v5.3.0.0
Win 11 Build 10.0.26200
plusminuseq
Bluetooth • XInput
33.15.12
🕹️
Stick LatencyP82
✓ Selected
5.2 ms
17.08 ms
33.9 ms
5.77 ms
67.52 Hz (see 📊)
#9173 • 2026-06-22
Prometheus 82 v5.3.0.0
Win 11 Build 10.0.26200
plusminuseq
Bluetooth • XInput
33.15.12
📊
Polling Rate
1.08 ms
14.81 ms
32.55 ms
7.05 ms
67.52 Hz
66.5 Hz
#9170 • 2026-06-22
Polling v2.0.2.5
Win 11 Build 10.0.26200
plusminuseq
Bluetooth • XInput
33.15.12
Note: This test are based on polling rate and do not represent actual input-lag.
More information

Latency

Our visualization focuses on Average Latency, presented as vertical bars to make comparing performance across different connection modes (Wired, Bluetooth, Dongle) instant and intuitive.

The chart differentiates between:

  • Button Latency: How quickly the game registers a physical button press.
  • Stick Latency: The delay in registering joystick movement (tested at 99% deflection).

Visualizing Stability (Jitter)

You may notice that the top portion of some bars is semi-transparent or "faded". This represents Jitter (instability):

  • Solid Bar: Represents the stable, consistent average latency.
  • Faded Top: Indicates the variance. A larger transparent area means higher jitter, implying the controller's response time fluctuates. A solid bar with little to no fading indicates a highly stable connection.

Deep Dive: Click the arrow to reveal Probability Distribution Charts. These show the exact breakdown of every input tested, displaying Probability (%) on the Y-axis and Latency (ms) on the X-axis.

Polling Rate vs. Latency

It is crucial to understand that Polling Rate and Latency are measured using two entirely different methodologies on our site:

  • Latency (ms) is measured by the Prometheus 82 hardware. It captures the physical movement of the stick or button via hardware interrupts with microsecond precision. This is the "real-world" delay.
  • Polling Rate (Hz) is measured via a Software Tool. It shows how often the OS receives reports from the USB stack.

Common Myth: A higher polling rate (like 8000 Hz) does not automatically guarantee lower latency if the controller's internal processing is slow. Conversely, a high polling rate on a chart might show fluctuations (e.g., 7800Hz instead of 8000Hz) due to OS jitter or CPU scheduling, which does not necessarily impact the hardware latency measured by the P82.

To test your own gamepad's polling rate, you can use our tool: Download Polling Rate Tester.

Testing Methods

Gamepadla ensures data integrity by combining three distinct testing methodologies:

  1. Prometheus 82 (P82): Our gold standard. A custom-built hardware device that physically actuates buttons and sticks. It uses high-speed hardware interrupts to capture events, making it independent of the controller's polling rate. It provides an error margin of only ±1ms for buttons and sticks. View on GitHub.

  2. GPDL Tester: An electrical monitoring tool for highly accurate button latency. While P82 simulates human-like mechanical movement, GPDL focuses on the electrical signal speed. View on GitHub.

  3. Software Polling Test: A pure software diagnostic to check communication frequency. We use this to verify if a controller actually reaches its advertised specs (e.g., 1000Hz or 8000Hz) at the OS level. Download Software.

Note: By comparing hardware-level latency (P82) with software-level reports (Polling Test), we can identify if a controller has "fake" high polling rates or poorly optimized firmware.

Stick test of Leadjoy Saber Plus

Stick test results for Leadjoy Saber Plus gamepad, by abhijit deol

Left Stick
Circle Error:1.0%
Eccentricity:0.6%
Center Error:0.4%
Resolution:8.0 bit256 steps
Right Stick
Circle Error:1.0%
Eccentricity:0.6%
Center Error:0.4%
Resolution:8.0 bit256 steps
OSWindows 11
Sys. nameWireless Controller
ModeSony
ConnectionDongle
Polling rate0 Hz
Tested onJune 24, 2026, 22:11

Errors Panel

Cardinal Snappingnone
Inner Deadzonenone
Center Skipnone
Low Resolutionnone
Incomplete Rangenone

Inner Deadzone

The Inner Deadzone is the area around the center of the stick where small movements are not registered. This helps prevent stick drift or accidental inputs, but if the deadzone is too large, it can make aiming less precise, especially in games requiring fine control. We evaluate the Inner Deadzone based on how much you need to move the stick before it responds—the less movement required, the better.

The Leadjoy Saber Plus has no Inner Deadzone. The stick responds immediately to even the slightest movement, which is excellent for aiming accuracy and micro-control. This makes it a great choice for precision-heavy games like first-person shooters (e.g., Valorant or Apex Legends).

For comparison, many budget gamepads often have a moderate to large Inner Deadzone, while premium controllers typically aim for a slight or no deadzone for better precision.

Want to learn more? Check out our video explanation of how the Inner Deadzone works.

Stick Eccentricity

Stick Eccentricity checks if the outer boundary is perfectly round. An uneven, egg-shaped boundary makes edge-aiming unpredictable. Lower is better.

For the Leadjoy Saber Plus, it's 0.6% (left) and 0.6% (right).

Testing Methodology: It's crucial to note that this test is performed at partial stick deflection (~80%), using special physical limiters (clips). Testing at 100% deflection often hides asymmetries because the controller's output is clamped at the maximum value, artificially 'smoothing' the resulting shape. Our method reveals the true performance of the stick in the ranges most critical for gameplay. This precise approach was also utilized by Linus Tech Tips in their controller review.

For comparison, many budget gamepads show asymmetry levels above 30%, while high-end controllers typically stay below 10% for better uniformity.

Learn more about how different gamepads perform in the Stick Asymmetry test and how to conduct such a test in this article. You can learn how to test joystick asymmetry yourself from this video.

Circle Error

Circle Error evaluates how closely the stick’s movement follows a perfect circle. A high Circle Error means the path is more square-like, which can cause inconsistent speeds when moving diagonally—your character might move faster or slower than expected. The lower the percentage, the better, as it ensures smooth, uniform movement in all directions.

For the Leadjoy Saber Plus, the Circle Error is 1.0% for the left stick and 1.0% for the right stick. This is an excellent result, providing smooth, natural diagonal movement similar to premium controllers.

For comparison, budget gamepads often have Circle Errors above 12%, resulting in 'square' feeling sticks, while high-quality ones aim for under 8% for better smoothness.

Want to learn more? Check out our video explanation of how Circle Error impacts performance.

Resolution (Stick Bitness)

Stick Bitness measures the precision of the joystick’s analog input, similar to bit depth in audio. Higher bitness means more distinct positions the stick can register, leading to smoother and more accurate control. Lower bitness can result in 'stepping' or less fluid movement, especially noticeable in slow, precise actions like aiming.

The Leadjoy Saber Plus has 8.0 bits on both sticks.

Note: Recorded with an older version before True Bitness.

This corresponds to a measured Step Resolution of 0.00781 on the left stick and 0.00781 on the right, with about 128 SFC on the left stick and 128 SFC on the right.

For comparison, many budget gamepads have around 8 bits, while premium ones often exceed 10 bits for superior accuracy.

Want to learn more? Check out our video explanation of how Stick Bitness affects control. It is important to note that the video specifies the resolution of the stick, not the bit depth; the higher the bit depth, the higher the resolution.

Center Error (Stick Centering)

Center Error (also referred to as Stick Centering) measures how accurately the joystick returns to its neutral (center) position after you release it. A low Center Error prevents stick drift—a common issue where your character or camera moves slightly in a game, even when you're not touching the stick. The lower the percentage, the better the centering, and the less likely you are to experience drift.

For the Leadjoy Saber Plus, the Center Error is 0.4% for the left joystick and 0.4% for the right stick. This is an excellent result. The sticks return almost perfectly to the center, which minimizes the risk of stick drift.

This test methodology intentionally employs a more rigorous approach by implementing small-angle deflection and release, which produces the most challenging conditions for stick re-centering. This technique differs from the conventional maximum-deflection method where the stick is pulled to its full range and released, as small-angle deflection better simulates the micro-adjustments typically executed during actual gameplay scenarios, providing more representative data on potential stick drift occurrence during normal use.

Want to learn more? Check out our video explanation of how Center Error works.

Cardinal Snapping

Cardinal Snapping (sometimes referred to as Axis Magnet) is a form of stick processing where the controller's output artificially 'snaps' or clings to the cardinal (horizontal and vertical) axes when the stick passes close to them. While this can make pure horizontal or vertical movements feel perfectly straight, it distorts the natural movement path and makes diagonal aiming or fine steering less predictable.

The Leadjoy Saber Plus shows no Cardinal Snapping. This means the stick does not artificially cling to the horizontal or vertical axes, preserving your real movement path for consistent aiming and natural analog control.

Want to learn more? Check out our video explanation of how Cardinal Snapping affects stick behavior.

Disclaimer

We tested the Leadjoy Saber Plus gamepad using a single unit, so keep in mind that other units of this model might perform slightly better or worse. In most cases, these differences are minor and shouldn’t affect your experience significantly. The results were obtained with the Stick Tracer program, and some values might vary if you use different software or testing methods.

Testing conditions, such as the gamepad’s firmware version (FW: ) or connection type, can also influence the results. If you have this gamepad, we’d love for you to share your own test results! This will help us build a more comprehensive picture of the Leadjoy Saber Plus’s performance across different units.

Full test results can be viewed on the test page.

Stick Movement Linearity Test

User experience surveys
Which connection modes work on Linux?
Shows which connection modes are supported on Linux and SteamOS, including Cable, Receiver, and Bluetooth.
Select all modes that apply
To join the survey, !

Leadjoy Saber Plus specifications

Internal

D-pad buttons type
Membrane
Main buttons type
Mechanical
Sticks type
TMR

External

Audio port
No
Button layout
Xbox
Display
No
Joystick positioning
Symmetric
Paddles
2
Rubber handles
No
Shoulder buttons
Yes
Stick tension
No
Trigger lock
Yes

Features

Gyroscope function
Yes
NFC support
No
Trigger vibration
No
Triggers pressing
Analog

Connection

Charging dock
No
USB interface
Type-C

Software

Firmware support
Yes
Macros option
Yes
Mobile software
Yes
No Dead Zone
Yes
PC software
Yes

Platforms

Linux
Yes
Nintendo Switch
Yes
Playstation 5
No
Windows
Cable, Receiver, Bluetooth
Xbox One
No
Xbox Series
No
Results based on answers from 3 users. Specifications are verified by moderators and reflect actual device behavior. Found a mistake? Hover over the specification to report it. Want to contribute? Join our questions survey!
User avatarUser avatarUser avatar

LatScore Comparison of Leadjoy Saber Plus

Users' opinion

Add your opinion
To add an opinion, you need to be !
No opinions have been added yet. Will you be the first?

User comments

You must to submit comment.

When are the center error results gonna be up?

2
12 days ago

Soon as I get time I will do full StickTracer tests.

2

@Danny89 Word. I just ordered one. I guess it will be here in a few weeks.

2

@Danny89 The best center error I seen on a low latency controller. Thank you.

2
edited 2 days ago

@Mass Controller Buyer That wasn't my test uploaded. I have been a bit too busy and also just lazy to test mine. I always test in raw mode as well. I will say that my center error is basically perfect, but this is because I have a lot of experience in fine tuning the center point on my controllers. I have a technique that allows me to match the center of physical slop with the calibrated center. The only gamepad this doesn't work for is G7 Pro/8K because something is wrong with the centering on those models. I still might test my Saber and upload, but honestly after years of searching and testing, the Saber is basically perfect to me so I've lost desire in testing further and have been spending more time actually gaming haha.

1

@Danny89 Gotcha. I am liking mine. The only thing I don’t like is the dpad. If I hit up somtimes it hits left or right. Membrane issues I assume but yes it’s perfect. I just set 1 deadzone for each stick in games just to cover micro hitter but it’s amazing. Thank you!

2
19 hours ago

@Mass Controller Buyer I personally prefer membrane d-pads over mechanical, but I agree that the d-pad on Saber is trash. It's way to easy to hit diagonal inputs. I haven't had the same issue as you, but I can definitely see how that is a problem for you friend. I use my GuliKit Elves 2 for anything d-pad centric, so it all works out haha.

1

@Danny89 That makes sense and I probably should bind stuff I need regarding the dpad to a back button or something. It’s mostly for cod when I’m doing a kill Streak or pinging which pinging is on the back button.

1