Telegram RegisterThe public register of Telegram
Telegram profile photo for Запрошуй та Заробляй

Bot

Запрошуй та Заробляй

@Referral_RewardsBot

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

18,887monthly users

-962 since we began measuring on 6 August 2026

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

Register entry

Telegram ID8788980339
TypeBot
Username@Referral_RewardsBot
First recorded16 August 2026
Last confirmed live18 August 2026
Measurements held7
Confirmed unchanged2 times, most recently 18 August 2026
On Telegramt.me/Referral_RewardsBot

Growth

18,88719,84919,3686 August 2026 — 19,849 monthly users10 August 2026 — 19,537 monthly users11 August 2026 — 19,497 monthly users12 August 2026 — 19,439 monthly users14 August 2026 — 19,319 monthly users16 August 2026 — 19,319 monthly users17 August 2026 — 18,887 monthly users6 August 202617 August 2026
7 measurements spanning 11 days, net -962. 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 18,743–19,993 and does not start at zero.
Measurement log — every monthly users count we have recorded
Measured (UTC)Monthly usersChange
17 Aug 2026, 10:3918,887-432
16 Aug 2026, 20:2419,319no change
14 Aug 2026, 07:4619,319-120
12 Aug 2026, 21:3719,439-58
11 Aug 2026, 02:1619,497-40
10 Aug 2026, 02:0219,537-312
6 Aug 2026, 21:0319,849first reading

Engagement

No post feed to measure. Telegram publishes a readable post stream for channels, not for bots, so views, reactions and engagement rates do not exist for this entry — they are not missing, pending or withheld. The register records what this handle is and what it resolves to.

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.

Mentions

Named by 30 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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 17 August 2026 — this entry's latest reading, not the date you are reading this.

“Запрошуй та Заробляй” (@Referral_RewardsBot), 18,887 monthly users as measured 17 August 2026. Telegram Register, tgregister.com/channel/Referral_RewardsBot.

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.