Telegram RegisterThe public register of Telegram
Telegram profile photo for گروه | کریپتو | ایردراپ

Supergroup

گروه | کریپتو | ایردراپ

@airdrrop_faarsi

Has discussion group

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

4,673members

-101 since we began measuring on 7 August 2026

20 online right now

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

Register entry

Telegram ID-1002094990218
TypeSupergroup
Username@airdrrop_faarsi
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live2 November 2026
Measurements held23
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/airdrrop_faarsi

Topic

Giveaways & airdrops — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 13 September 2026 and assigned it the closest of 31 fixed categories, at 62% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

4,6704,7744,7227 August 2026 — 4,774 members11 August 2026 — 4,769 members14 August 2026 — 4,760 members17 August 2026 — 4,755 members20 August 2026 — 4,753 members24 August 2026 — 4,748 members27 August 2026 — 4,735 members30 August 2026 — 4,732 members2 September 2026 — 4,729 members2 September 2026 — 4,729 members6 September 2026 — 4,718 members11 September 2026 — 4,716 members14 September 2026 — 4,715 members19 September 2026 — 4,704 members29 September 2026 — 4,703 members6 October 2026 — 4,697 members12 October 2026 — 4,680 members15 October 2026 — 4,673 members18 October 2026 — 4,680 members24 October 2026 — 4,678 members27 October 2026 — 4,676 members30 October 2026 — 4,670 members2 November 2026 — 4,673 members4,6737 August 20262 November 2026
23 measurements spanning 86 days, net -101. 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 4,654–4,790 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 23
Measured (UTC)MembersChange
2 Nov 2026, 00:094,673+3
30 Oct 2026, 04:304,670-6
27 Oct 2026, 08:294,676-2
24 Oct 2026, 13:464,678-2
18 Oct 2026, 16:014,680+7
15 Oct 2026, 19:394,673-7
12 Oct 2026, 22:374,680-17
6 Oct 2026, 06:594,697-6
29 Sept 2026, 08:204,703-1
19 Sept 2026, 02:184,704-11
14 Sept 2026, 13:174,715-1
11 Sept 2026, 07:414,716-2
6 Sept 2026, 10:204,718-11
2 Sept 2026, 19:084,729no change
2 Sept 2026, 07:044,729-3
30 Aug 2026, 11:544,732-3
27 Aug 2026, 05:454,735-13
24 Aug 2026, 06:184,748-5
20 Aug 2026, 10:174,753-2
17 Aug 2026, 19:484,755first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind 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 2 November 2026 — this entry's latest reading, not the date you are reading this.

“گروه | کریپتو | ایردراپ” (@airdrrop_faarsi), 4,673 members as measured 2 November 2026. Telegram Register, tgregister.com/channel/airdrrop_faarsi.

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.