Channel
Green Feel 🌿
@greenfeell
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
4,336subscribers
-18 since we began measuring on 5 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001013563097 |
|---|---|
| Type | Channel |
| Username | @greenfeell |
| Created | Between 1 December 2015 and 31 March 2016 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 3 September 2026 |
| Last confirmed live | 13 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 13 September 2026 |
| On Telegram | t.me/greenfeell |
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 13 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Sept 2026, 14:17 | 4,336 | -2 |
| 9 Sept 2026, 19:58 | 4,338 | -2 |
| 4 Sept 2026, 05:00 | 4,340 | -1 |
| 3 Sept 2026, 23:22 | 4,341 | no change |
| 31 Aug 2026, 15:25 | 4,341 | +1 |
| 24 Aug 2026, 23:57 | 4,340 | -2 |
| 21 Aug 2026, 11:43 | 4,342 | -1 |
| 18 Aug 2026, 18:56 | 4,343 | -4 |
| 15 Aug 2026, 17:54 | 4,347 | -3 |
| 12 Aug 2026, 01:33 | 4,350 | -3 |
| 9 Aug 2026, 11:07 | 4,353 | -1 |
| 5 Aug 2026, 21:14 | 4,354 | 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.
@biijameart · 34,159
Telegram ranks this channel #19 of 81 here — alongside 80 others — read 3 September 2026
@thepanizgm · 35,787
Telegram ranks this channel #22 of 90 here — alongside 89 others — read 2 September 2026
@cafeparagraph_mag · 61,884
Telegram ranks this channel #23 of 90 here — alongside 89 others — read 22 August 2026
@Madamekotrelchannel · 35,205
Telegram ranks this channel #26 of 83 here — alongside 82 others — read 2 September 2026
@amiralichannel · 68,600
Telegram ranks this channel #44 of 93 here — alongside 92 others — read 20 August 2026
@baycot · 149,666
Telegram ranks this channel #52 of 91 here — alongside 90 others — read 12 August 2026
This channel appears in 6 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 13 September 2026 — this entry's latest reading, not the date you are reading this.
“Green Feel 🌿” (@greenfeell), 4,336 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/greenfeell.
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.