
Channel
Jacob Forever
@JacobForever
On this record: Growth · Engagement · Cite this entry
6,320subscribers
-125 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
Register entry
| Telegram ID | -1001213513585 |
|---|---|
| Type | Channel |
| Username | @JacobForever |
| Created | Between 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 28 August 2026 |
| Last confirmed live | 4 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 4 September 2026 |
| On Telegram | t.me/JacobForever |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 4 Sept 2026, 19:56 | 6,320 | -10 |
| 1 Sept 2026, 12:03 | 6,330 | -7 |
| 29 Aug 2026, 03:54 | 6,337 | -9 |
| 28 Aug 2026, 21:38 | 6,346 | no change |
| 26 Aug 2026, 02:49 | 6,346 | -8 |
| 22 Aug 2026, 23:52 | 6,354 | -15 |
| 19 Aug 2026, 13:32 | 6,369 | -24 |
| 16 Aug 2026, 18:23 | 6,393 | -15 |
| 13 Aug 2026, 13:59 | 6,408 | -20 |
| 10 Aug 2026, 06:36 | 6,428 | -16 |
| 7 Aug 2026, 10:30 | 6,444 | -1 |
| 6 Aug 2026, 20:55 | 6,445 | 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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Jacob Forever” (@JacobForever), 6,320 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/JacobForever.
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.