I once again humbly ask CF admins/moderators to fill in ratings for problems from latest contests. Please, do this, it's been more than a month since the last update.
| # | User | Rating |
|---|---|---|
| 1 | jiangly | 3810 |
| 2 | Benq | 3676 |
| 3 | Kevin114514 | 3655 |
| 4 | maroonrk | 3463 |
| 5 | strapple | 3390 |
| 6 | Um_nik | 3387 |
| 7 | tourist | 3384 |
| 8 | heuristica | 3322 |
| 9 | turmax | 3319 |
| 10 | jiangbowen | 3291 |
| # | User | Contrib. |
|---|---|---|
| 1 | Qingyu | 155 |
| 2 | nik_exists | 150 |
| 2 | maspy | 150 |
| 4 | Um_nik | 143 |
| 5 | AmShZ | 140 |
| 6 | Errichto | 139 |
| 7 | adamant | 137 |
| 8 | maroonrk | 134 |
| 9 | BledDest | 132 |
| 10 | qwexd | 129 |
I once again humbly ask CF admins/moderators to fill in ratings for problems from latest contests. Please, do this, it's been more than a month since the last update.
| Name |
|---|



You can use clist.by to see estimations of problem ratings. I believe a problem's estimated rating is calculated based on the ratings of contestants. The estimations are not necessarily the same as what appears on Codeforces, but I find that they are consistently close (within ~100) and feel reasonable.
I know about clist
I agree with you!
CF gods heard your call!
Yep, thanks to them