Telegram RegisterThe public register of Telegram
Telegram profile photo for Тунис (попутчики) 🩳🐚👙

Supergroup

Тунис (попутчики) 🩳🐚👙

@tunis4at

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

1,832members

-145 since we began measuring on 7 August 2026

116 online right now

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

Register entry

Telegram ID-1001256119941
TypeSupergroup
Username@tunis4at
CreatedBetween 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded23 September 2026
Last confirmed live2 November 2026
Measurements held25
Confirmed unchanged1 time, most recently 2 November 2026
On Telegramt.me/tunis4at

Topic

Travel — 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 23 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

1,4731,9771,7257 August 2026 — 1,977 members7 August 2026 — 1,973 members10 August 2026 — 1,954 members13 August 2026 — 1,473 members16 August 2026 — 1,484 members19 August 2026 — 1,506 members23 August 2026 — 1,544 members26 August 2026 — 1,564 members29 August 2026 — 1,599 members1 September 2026 — 1,639 members5 September 2026 — 1,664 members10 September 2026 — 1,716 members14 September 2026 — 1,750 members18 September 2026 — 1,793 members23 September 2026 — 1,793 members27 September 2026 — 1,827 members5 October 2026 — 1,804 members12 October 2026 — 1,783 members15 October 2026 — 1,763 members18 October 2026 — 1,745 members22 October 2026 — 1,763 members25 October 2026 — 1,789 members27 October 2026 — 1,806 members30 October 2026 — 1,809 members2 November 2026 — 1,832 members1,8327 August 20262 November 2026
25 measurements spanning 88 days, net -145. 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 1,397–2,053 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 25
Measured (UTC)MembersChange
2 Nov 2026, 18:361,832+23
30 Oct 2026, 18:581,809+3
27 Oct 2026, 23:361,806+17
25 Oct 2026, 03:161,789+26
22 Oct 2026, 06:091,763+18
18 Oct 2026, 18:191,745-18
15 Oct 2026, 22:281,763-20
12 Oct 2026, 15:581,783-21
5 Oct 2026, 15:191,804-23
27 Sept 2026, 13:011,827+34
23 Sept 2026, 15:401,793no change
18 Sept 2026, 07:371,793+43
14 Sept 2026, 01:571,750+34
10 Sept 2026, 17:411,716+52
5 Sept 2026, 14:391,664+25
1 Sept 2026, 11:341,639+40
29 Aug 2026, 03:031,599+35
26 Aug 2026, 02:191,564+20
23 Aug 2026, 10:381,544+38
19 Aug 2026, 12:511,506first 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.

“Тунис (попутчики) 🩳🐚👙” (@tunis4at), 1,832 members as measured 2 November 2026. Telegram Register, tgregister.com/channel/tunis4at.

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.