What is it?
Number Pad (10-Key) Practice trains fast, accurate number entry for accounts, billing, banking and data entry. Your right hand rests on 4 5 6 (5 has a bump); the index finger also covers 7 and 1, the middle 8 and 2, the ring 9, 3 and the decimal point, and the thumb presses 0. Results are in keystrokes per hour (KPH), the usual 10-key measure.
Who is it for?
Accountants and billing staff, data-entry job applicants, bank and shop cashiers, and commerce students.
How to use it
- Choose Practise: 4 5 6, + 7 8 9, + 1 2 3, + 0 and ., All, Amounts or Long IDs.
- Rest your right hand on 4 5 6. “Type each number and press Enter”.
- Follow the lit-up key and the finger named under the pad.
- See your KPH and accuracy (“… KPH at …%”) and press Next set; New set skips.
What is a good speed?
The tool’s own note says data-entry jobs often ask for 8,000–12,000 KPH with high accuracy; beginners usually start well below that. Pressing Enter after each number matches real forms and spreadsheets.
Worked example
In 2 minutes you type 300 keystrokes (digits, points and Enters) correctly: 300 × 30 = 9,000 KPH. Keep your eyes on the numbers, not the pad, and remember that one wrong digit in an amount can cost money, so accuracy comes first.
Errors and how to fix them
- Nothing types on the pad: press Num Lock so its light is on.
- A letter turns red: you pressed the wrong key. Press Backspace and type the right one. Mistakes you leave in lower your accuracy.
- No number pad on my laptop: use the top-row digits for now, or a cheap USB number pad; the levels still teach the right fingers.
- My best score or past results are gone: results are kept only in this browser on this device. Clearing browsing data, private/incognito mode or another browser or phone starts fresh.
Open the tool: Number Pad (10-Key) Practice
Still stuck?
Contact support. Tell us which tool or page you were using, what you tapped, what you saw, and your phone or computer and browser (for example: Android phone, Chrome). We reply by email.






























Questions, or an error not listed here?
Tell us in the comments: what you were doing, the exact message you saw, and your device and browser. We read every comment and add new fixes to this article.