Use ZRANK to get the position of a member in a sorted set, counting from the lowest score.
The rank is zero-based, so the lowest scoring member has rank 0, and members with equal scores are ordered lexicographically. WITHSCORE returns the score alongside the rank. The reply is null when the member or the key does not exist.
This is how a leaderboard reports "you are number N": increment scores with ZINCRBY and read the position back here, using ZREVRANK when rank 0 should be the highest score instead.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
<member> | Yes | No | Member name. |
WITHSCORE | No | No | Also return the member's score alongside its rank. |
Important points#
- RESP2 represents floating-point reply values as bulk strings; RESP3 may use native double replies. Client libraries commonly decode either form to a language number.
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Null bulk string or null array, Integer, or two-element rank/score array |
| RESP3 | Null, Integer, or two-element rank/score array |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.