What topics does the 1300 CP-31 sheet cover?
Mostly counting with hash maps, prefix sums, two pointers, greedy with sorting and early bitwise reasoning like XOR properties. It is where Div. 2 C starts.
Priyansh Agarwal
Curated by Priyansh Agarwal, ICPC World Finalist and AIR 1 in Google Kick Start, this sheet features all essential 1300-rated Codeforces questions. With a Master (India Rank 34) on Codeforces and 4000+ students taught, Priyansh’s expertise ensures that this sheet will help you sharpen your competitive programming skills and make steady progress
1300 on Codeforces is Pupil level. Pupils who solve Div. 2 B quickly but get Div. 2 C in fewer than half their contests.
What these problems lean on: Prefix sums with hashing, Counting pairs, Greedy + sorting, Bit manipulation basics, Two pointers.
The usual wall at 1300: Counting problems — "how many pairs (i, j) satisfy…" — need you to fix one index and count the other with a map, instead of looping over both.
How to practise it: For every pair-counting problem, ask what j must be for a fixed i, then count those with a frequency map. That single trick covers a large share of this sheet.
0%
0/31
Overall progress
0 / 31
0/1
Easy
0/29
Medium
0/1
Hard
Mostly counting with hash maps, prefix sums, two pointers, greedy with sorting and early bitwise reasoning like XOR properties. It is where Div. 2 C starts.
Around 30–45 minutes when you are working at your level. If you consistently solve them in under 20, move to 1400.
There is no PDF here, and you do not need one. All 31 problems are listed in full on this page, free and without an account — and unlike a PDF the list remembers what you have ticked off, so you are not re-reading a static file to work out where you stopped. Use your browser's print view if you want it on paper.
Tick a problem on this page and it stays ticked. Progress saves in your browser straight away with no account, and the counts update per section so you can see which parts of 1300 Rated: CP-31 Sheet you have actually covered. Signing in with Google syncs it across devices.
At roughly 25 minutes a problem — reading it, solving it and writing the approach down — 31 problems is about 13 hours, or 1 weeks at ten hours a week. Treat that as a planning figure rather than a promise; the first pass through an unfamiliar topic is always slower.
Yes, completely, and no account is needed. There is no paid tier and nothing is held back — the sheet itself is by Priyansh Agarwal, and this is a free tracker for it.
Finish one. Sheets overlap heavily, so working several in parallel mostly means re-solving the same problems while never completing a full topic sweep. If you are not sure this is the right one for the time you have, the sheet comparison page puts the options side by side with hour estimates.