Channel
@jamescaspian1
On this record: Growth ยท Engagement ยท What this channel posts ยท Reactions ยท Posts ยท Telegram's recommendations ยท Cite this entry
500subscribers
+0 since we began measuring on 7 September 2026
Risers and fallers across the register ยท movement among entries of Under 1,000.
| Telegram ID | -1002055098740 |
|---|---|
| Type | Channel |
| Username | @jamescaspian1 |
| Created | Between 1 November 2023 and 31 May 2024 โ estimated from Telegramโs id allocation, not measured. How this range is calculated. |
| First recorded | 7 September 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 2 |
| On Telegram | t.me/jamescaspian1 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 15:23 | 500 | no change |
| 7 Sept 2026, 07:47 | 500 | first reading |
20 posts held, back to 24 July 2024 โ 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 20 posts for this entry, the most recent from 16 March 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegramโs own channel header, read 7 September 2026 โ not the date at the top of this page, which is when the subscriber count was last read. Below Telegramโs rounding threshold, so these counts are exact.
Measured directly from 19 videos with a duration reading, out of the posts we hold for this channel โ not this channelโs whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegramโs own rounded chrome, so it carries no โ mark.
318 reactions across 19 posts, in 11 distinct kinds. The most used accounts for 73.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| โค | 234 | 73.6% | |
| โคโ๐ฅ | 38 | 11.9% | |
| ๐ | 12 | 3.77% | |
| ๐ | 11 | 3.46% | |
| โ | 9 | 2.83% | |
| ๐ | 4 | 1.26% | |
| ๐ฅฐ | 3 | 0.943% | |
| ๐ | 2 | 0.629% | |
| ๐ฅ | 2 | 0.629% | |
| ๐ค | 2 | 0.629% | |
| ๐ | 1 | 0.314% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities โ ๐ is thanks in one channel and mourning in another โ so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one โ 4.34K, 1.2M โ so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegramโs own count on each post โ not by adding up the per-emoji breakdown above โ those same posts carry 318 reactions in total: the kind of figure the paragraph above means by โa reaction total printed elsewhere on the pageโ.
Measured over the 20 most recent posts we hold, published 24 July 2024 to 16 March 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
The owner of this channel has been inactive for the last 17 months. If they remain inactive for the next 10 days, they may lose their account and admin rights in this channel. The contents of the channel will remain accessible for all users.
๐๐ซ๐๐ฏ๐ (๐๐๐๐) ๐น
โค13
โแกแฒแทแแฑแทแ แแญแฏแแบแแแบแธแแญแฏ แแผแแบแแแบ แแแบแธแแ แบแแฑแฌแแบแแฒแแญแฏแแฒ แแผแแบแแฒแทแแฌโ
โค24๐1
๐๐ซ๐๐๐จ ๐๐๐ฅ๐๐จ๐ฒ ๐๐
โคโ๐ฅ21๐ฅฐ1
๐ ๐ฅ๐จ๐ฏ๐ ๐ฒ๐จ๐ฎ ๐ฆ๐จ๐ซ๐ ๐ญ๐ก๐๐ง ๐๐ง๐ฒ ๐ ๐ข๐ซ๐ฅ ๐'๐ฏ๐ ๐๐ฏ๐๐ซ ๐ค๐ง๐จ๐ฐ๐ง.๐๐ฉต
๐12๐ฅ2
๐๐๐ฉ๐ญ๐๐ฆ๐๐๐ซ ๐๐ฌ๐ญ, ๐๐๐๐ค ๐ญ๐จ ๐๐จ๐ ๐ฐ๐๐ซ๐ญ๐ฌ. ๐
โคโ๐ฅ7โค4
๐๐จ๐จ๐๐๐ฒ๐ ๐๐ฎ๐ ๐ฎ๐ฌ๐ญ ๐ฟ
๐11โค7
_๐๐ข๐ง๐๐๐ซ๐๐ฅ๐ฅ๐ (๐๐๐๐) ๐
โค17
๐๐จ๐ญ๐จ๐ซ๐จ _โ ห๐ฬ!!
โคโ๐ฅ10โค6๐4
๐๐๐ฉ๐ฉ๐ฒ ๐๐๐ญ๐ข๐จ๐ง๐๐ฅ ๐ ๐ซ๐ข๐๐ง๐๐ฌ๐ก๐ข๐ฉ ๐๐๐ฒ ๐๐
โค19๐ค2
๐ฟ ๐๐ฎ๐ ๐ฎ๐ฌ๐ญ || ๐๐๐ฒ๐ฅ๐จ๐ซ ๐๐ฐ๐ข๐๐ญ
โค22
๐๐๐ซ๐ฅ๐๐ฒ ๐๐ฎ๐ข๐ง๐ง
โค10
Showing the 12 most recent of 20 posts we hold for @jamescaspian1. 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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegramโs list for THAT channel, not this one โ see how this is measured.
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 7 September 2026 โ this entry's latest reading, not the date you are reading this.
โ๐๐๐๐๐๐๐ใโ (@jamescaspian1), 500 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/jamescaspian1.
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.