Channel
WorkTrove - Internships Jobs Opportunities
@WorkTrove
On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry
1,259subscribers
-49 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 | -1001726605832 |
|---|---|
| Type | Channel |
| Username | @WorkTrove |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 2 October 2026 |
| Last confirmed live | 4 November 2026 |
| Measurements held | 21 |
| Confirmed unchanged | 1 time, most recently 4 November 2026 |
| On Telegram | t.me/WorkTrove |
Topic
Job listings — 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 2 October 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
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Nov 2026, 22:20 | 1,259 | -1 |
| 1 Nov 2026, 14:40 | 1,260 | -1 |
| 30 Oct 2026, 00:29 | 1,261 | -3 |
| 27 Oct 2026, 08:37 | 1,264 | -1 |
| 21 Oct 2026, 09:46 | 1,265 | -3 |
| 18 Oct 2026, 11:30 | 1,268 | -2 |
| 15 Oct 2026, 08:27 | 1,270 | -3 |
| 12 Oct 2026, 06:01 | 1,273 | -4 |
| 5 Oct 2026, 10:21 | 1,277 | -4 |
| 2 Oct 2026, 17:08 | 1,281 | no change |
| 27 Sept 2026, 13:17 | 1,281 | -5 |
| 15 Sept 2026, 20:40 | 1,286 | -1 |
| 11 Sept 2026, 20:42 | 1,287 | -4 |
| 7 Sept 2026, 00:59 | 1,291 | -2 |
| 2 Sept 2026, 13:03 | 1,293 | -2 |
| 30 Aug 2026, 11:14 | 1,295 | -4 |
| 24 Aug 2026, 09:37 | 1,299 | -4 |
| 20 Aug 2026, 14:53 | 1,303 | -4 |
| 17 Aug 2026, 18:46 | 1,307 | +1 |
| 11 Aug 2026, 08:32 | 1,306 | 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.
@arunchauhanofficial · 53,669
Telegram ranks this channel #40 of 71 here — alongside 70 others — read 23 August 2026
@officialresultbharat · 39,717
Telegram ranks this channel #50 of 53 here — alongside 52 others — read 30 August 2026
@reasoning_byashusir · 39,614
Telegram ranks this channel #54 of 56 here — alongside 55 others — read 30 August 2026
@education_portal_rajasthan · 56,430
Telegram ranks this channel #73 of 74 here — alongside 73 others — read 23 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 4 November 2026 — this entry's latest reading, not the date you are reading this.
“WorkTrove - Internships Jobs Opportunities” (@WorkTrove), 1,259 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/WorkTrove.
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.