GOL 19 pinned a photo

Channel
GOL 19
@pishbinGol
On this record: Topic · Growth · Engagement · Posts · Cite this entry
2,440subscribers
+40 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001071568019 |
|---|---|
| Type | Channel |
| Username | @pishbinGol |
| Created | Between 1 October 2016 and 31 July 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 September 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 24 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/pishbinGol |
Topic
Sports — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 22:48 | 2,440 | +6 |
| 1 Nov 2026, 23:35 | 2,434 | -5 |
| 29 Oct 2026, 21:34 | 2,439 | +2 |
| 23 Oct 2026, 17:58 | 2,437 | +5 |
| 20 Oct 2026, 15:09 | 2,432 | -1 |
| 17 Oct 2026, 18:51 | 2,433 | +4 |
| 14 Oct 2026, 11:01 | 2,429 | +1 |
| 10 Oct 2026, 21:20 | 2,428 | -1 |
| 5 Oct 2026, 02:20 | 2,429 | -8 |
| 26 Sept 2026, 12:42 | 2,437 | -1 |
| 17 Sept 2026, 17:39 | 2,438 | +5 |
| 13 Sept 2026, 07:58 | 2,433 | +7 |
| 9 Sept 2026, 10:36 | 2,426 | +11 |
| 6 Sept 2026, 16:22 | 2,415 | no change |
| 4 Sept 2026, 02:22 | 2,415 | -2 |
| 31 Aug 2026, 05:54 | 2,417 | +4 |
| 27 Aug 2026, 23:43 | 2,413 | +4 |
| 24 Aug 2026, 23:42 | 2,409 | +8 |
| 20 Aug 2026, 23:57 | 2,401 | +2 |
| 17 Aug 2026, 18:06 | 2,399 | first reading |
Engagement
11 posts held, back to 5 September 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 11 posts for this entry, the most recent from 6 September 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
بولتن یکشنبه دوره 44 لطفا به بازی های جایگزین شده توجه کنید‼️
Photo, posted without a caption
نفرات دوم 19 بازی شنبه دوره 43
نفرات اول 19 بازی شنبه دوره 43
19 بازی شنبه دوره 43
Photo, posted without a caption
Photo, posted without a caption
File, posted without a caption
File, posted without a caption
File, posted without a caption
Showing the 11 most recent of 11 posts we hold for @pishbinGol. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.
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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“GOL 19” (@pishbinGol), 2,440 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/pishbinGol.
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.