Channel
گوجه گیلاسی با نمک.
@tomatoooooooooooooooo
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
3,547subscribers
-54 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001982275942 |
|---|---|
| Type | Channel |
| Username | @tomatoooooooooooooooo |
| Created | Between 1 April 2023 and 31 October 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 2 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 2 November 2026 |
| On Telegram | t.me/tomatoooooooooooooooo |
Topic
Other / unclassifiable — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 |
|---|---|---|
| 2 Nov 2026, 14:26 | 3,547 | -2 |
| 27 Oct 2026, 07:57 | 3,549 | -4 |
| 24 Oct 2026, 01:30 | 3,553 | -1 |
| 20 Oct 2026, 18:38 | 3,554 | +1 |
| 17 Oct 2026, 22:59 | 3,553 | -6 |
| 12 Oct 2026, 01:21 | 3,559 | -14 |
| 5 Oct 2026, 01:58 | 3,573 | +2 |
| 26 Sept 2026, 02:59 | 3,571 | -10 |
| 15 Sept 2026, 20:15 | 3,581 | -5 |
| 12 Sept 2026, 01:18 | 3,586 | +2 |
| 7 Sept 2026, 22:43 | 3,584 | no change |
| 7 Sept 2026, 21:57 | 3,584 | -3 |
| 2 Sept 2026, 20:19 | 3,587 | -6 |
| 30 Aug 2026, 20:14 | 3,593 | -3 |
| 27 Aug 2026, 22:55 | 3,596 | +7 |
| 21 Aug 2026, 04:16 | 3,589 | +2 |
| 18 Aug 2026, 00:02 | 3,587 | -1 |
| 14 Aug 2026, 13:45 | 3,588 | -9 |
| 11 Aug 2026, 05:08 | 3,597 | -2 |
| 8 Aug 2026, 08:57 | 3,599 | first 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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@donteatthishit · 69,883
Telegram ranks this channel #2 of 79 here — alongside 78 others — read 20 August 2026
@djmohrezremix · 81,807
Telegram ranks this channel #47 of 49 here — alongside 48 others — read 19 August 2026
@mymusicx · 34,052
Telegram ranks this channel #58 of 77 here — alongside 76 others — read 3 September 2026
@BadVirall · 106,341
Telegram ranks this channel #76 of 89 here — alongside 88 others — read 20 August 2026
This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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.
“گوجه گیلاسی با نمک.” (@tomatoooooooooooooooo), 3,547 subscribers as measured 2 November 2026. Telegram Register, tgregister.com/channel/tomatoooooooooooooooo.
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.