LeetCode Stopwatch
by Tuan Chau more by this developer →
#146,419 of 270,598 by installs on Chrome · #89,296 of 163,799 in productivity
First seen by this census 09/01/2026 — the store does not publish a creation date
Last updated 05/27/2024
Tracked since 09/01/2026
Compare with another extension
Category: productivity / developer
Languages: English (United States)
Description
This extension customizes the LeetCode website
Alternatives to LeetCode Stopwatch
| Name | Users | Rating | |
|---|---|---|---|
Cadence - LeetCode Attempt Stopwatch
by Cadence
|
3 | — | compare |
Alarm, Timer and Stopwatch
by brian.girko
|
80,000 | 4.4 | compare |
Leetcode helper by labuladong
|
40,000 | 4.8 | compare |
LeetSync - Leetcode to Github Synchronizer
by Ahmed Ghonem
|
40,000 | 3.5 | compare |
Timer, Alarm & Stopwatch
by leocompson
|
30,000 | 3.1 | compare |
LeetCode Video Solutions
|
20,000 | 4.4 | compare |
Leetcode Enhancer
by Lovesh Dongre
|
10,000 | 3.8 | compare |
LeetCode Timer
by Bhanu Prakash
|
10,000 | 4.3 | compare |
Stopwatch for Google Chrome™
|
10,000 | 4.8 | compare |
Leetcode Explained
|
9,000 | 2.9 | compare |
Growth
Change in installs. This store publishes the count rounded to one or two significant figures, so it does not move when the listing grows - it moves when the rounding rolls over. The figures below are therefore what was actually observed between the two crawls named in "measured over", not scaled to the window, and the percentage is of that same rounding step - so a small listing crossing a bucket shows a very large one. A window needs a full period of history before it reports anything.
| Per | Growth | Growth % | Actual change | Measured over |
|---|---|---|---|---|
| day | Not enough history yet | |||
| week | Not enough history yet | |||
| month | Not enough history yet | |||
| year | Not enough history yet | |||