Channel
@jamesbylaufey
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
422subscribers
+15 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003595566409 |
|---|---|
| Type | Channel |
| Username | @jamesbylaufey |
| Created | Between 1 December 2025 and 31 May 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 15 August 2026 |
| On Telegram | t.me/jamesbylaufey |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Aug 2026, 02:06 | 422 | +9 |
| 7 Aug 2026, 12:40 | 413 | +6 |
| 6 Aug 2026, 19:51 | 407 | first reading |
17 posts held, back to 1 August 2026 — 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 16 of 17 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 August 2026 |
|---|---|
| Posts held | 17 (1 August 2026 – 6 August 2026) |
| Views total | 3,375 |
| Reactions total | 789 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 6 Aug 2026, 19:51 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
789 reactions across 16 posts, in 4 distinct kinds. The most used accounts for 27.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5436273456691845523 | 213 | 27.0% | |
| custom 5341323270354397397 | 209 | 26.5% | |
| custom 5341464106627003431 | 185 | 23.4% | |
| custom 5451743602474522490 | 182 | 23.1% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.
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 16 of the 17 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 789reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 17 most recent posts we hold, published 1 August 2026 to 6 August 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.
going REDRED like hot cheetos good hit like these channels 🤩 : boys : ✶ cortis : cortis 🤩 james 🤩 martin 🤩 seonghyeon 🤩 juhoon 🤩 keonho 🌟 seonghyeon 🤩 keonho 🤩 seonghyeon 🤩 juhoon 🌟 seonghyeon 🤩 keonho 🤩 ✶ txt : beomgyu & yeonjun 🤩 ✶ enhypen : jake 🤩 jake & sunghoon 🤩 sunoo & ni-ki 🤩 jakewon 🤩 sunoo & jake 🤩 jay & jake & sunghoon 🤩 sunoo & jay 🤩 jungwon & ni-ki 🤩 sunghoon & ni-ki 🤩 ✶ ald1 : sangwon 🤩 geonwoo 🤩 san…
happy 400~ love y’all 🫂
custom 53413232703543973976custom 54362734566918455236custom 53414641066270034315custom 54517436024745224903
Posted without readable text
custom 543627345669184552311custom 53413232703543973978custom 53414641066270034316custom 54517436024745224904
Posted without readable text
custom 534146410662700343112custom 534132327035439739711custom 543627345669184552310custom 54517436024745224909
Posted without readable text
custom 534132327035439739716custom 545174360247452249012custom 534146410662700343110custom 543627345669184552310
Posted without readable text
custom 534132327035439739713custom 543627345669184552311custom 545174360247452249010custom 53414641066270034318
табло составил топ-5 кортис, и на второе место поставил еще не выпущенную nani 💧 he’s one of us tablo почему вы не релизнули эту песню? зачем вы нас троллите? вы, ребята, даже снимали с ней шортсы. вы забыли? выглядит так, будто вы забыли Y 凡 это было разовое событие, потому что мы снимались на японском шоу. и если честно, хуком было то, что нам бесплатно дали поработать с vision pro от apple tablo то есть вы хотите…
custom 534132327035439739715custom 545174360247452249010custom 53414641066270034319custom 54362734566918455238
tablo у вас даже есть строчка с MJ martin я написал ее, но я даже не помню, что она значила.. tablo что ты имеешь ввиду? ты же написал ее?! martin я написал, но это было так давно. и когда я пытаюсь вспомнить, я думаю «что я вообще имел ввиду» Y 凡 но фанаты очень хорошо это обыграли. типа мартин и джеймс вместе с 2023 martin но я думаю, я это и имел ввиду
custom 545174360247452249014custom 534132327035439739711custom 54362734566918455239custom 53414641066270034317
tablo ты же любишь мятный шоколад? и гавайскую пиццу? martin yeah~ tablo серьезно, если у вас есть проблемы с этим, f* you Y 凡 F* ME THEN tablo прости, джеймс. ты не любишь гавайскую пиццу? Y 凡 нет, я как бы враг мартина
custom 534132327035439739717custom 543627345669184552313custom 53414641066270034319custom 54517436024745224907
Posted without readable text
custom 543627345669184552317custom 534132327035439739711custom 534146410662700343111custom 54517436024745224906
04/07 PRODZ PODCAST feat. tablo 🎙️ Y 凡 когда мы ездим в японию или в америку, мы занимаем один гостиничный номер martin в последнее время такое бывает очень часто Y 凡 мы соседи по комнате, и как-то ему пришлось слушать эхо-версию hey tablo tablo потому что ты слушаешь мои подкасты в душе? тот факт, что джеймс слушает мой голос, пока принимает душ, просто дикий, но и лестный тоже
custom 534146410662700343115custom 543627345669184552312custom 534132327035439739711custom 54517436024745224906
тред готов к вашему прочтению !
custom 534132327035439739714custom 534146410662700343112custom 543627345669184552312custom 54517436024745224909
Showing the 12 most recent of 17 posts we hold for @jamesbylaufey. 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.
Citation-graph rank — 138,819 of 1,481,306entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 53 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 15 August 2026 — this entry's latest reading, not the date you are reading this.
“jamie” (@jamesbylaufey), 422 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/jamesbylaufey.
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.