Telegram RegisterThe public register of Telegram
Telegram profile photo for UnionPay в России

Supergroup

UnionPay в России

@unionpayru

Has discussion group

On this record: Growth · Engagement · Citations · Cite this entry

39,269members

+112 since we began measuring on 6 August 2026

8,410 online right now

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001414009588
TypeSupergroup
Username@unionpayru
CreatedBetween 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 August 2026
Last confirmed live16 August 2026
Measurements held11
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/unionpayru

Growth

39,15739,26939,2136 August 2026 — 39,157 members7 August 2026 — 39,178 members8 August 2026 — 39,179 members9 August 2026 — 39,180 members10 August 2026 — 39,191 members11 August 2026 — 39,201 members12 August 2026 — 39,232 members13 August 2026 — 39,232 members14 August 2026 — 39,244 members15 August 2026 — 39,261 members16 August 2026 — 39,269 members6 August 202616 August 2026
11 measurements spanning 10 days, net +112. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 39,140–39,286 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
16 Aug 2026, 16:4539,269+8
15 Aug 2026, 04:4939,261+17
14 Aug 2026, 00:4439,244+12
13 Aug 2026, 02:1839,232no change
12 Aug 2026, 17:2239,232+31
11 Aug 2026, 14:3139,201+10
10 Aug 2026, 12:2739,191+11
9 Aug 2026, 15:2139,180+1
8 Aug 2026, 14:5039,179+1
7 Aug 2026, 12:0639,178+21
6 Aug 2026, 15:4939,157first reading

Engagement

No public post preview. We read this entry on 13 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Citation-graph rank

Citation-graph rank — 757,378 of 1,481,243entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 16 August 2026 — this entry's latest reading, not the date you are reading this.

“UnionPay в России” (@unionpayru), 39,269 members as measured 16 August 2026. Telegram Register, tgregister.com/channel/unionpayru.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.