Telegram RegisterThe public register of Telegram

Channel

JDM confession 🚗🇯🇵

@jdm_cf

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

26subscribers

+0 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003704746843
TypeChannel
Username@jdm_cf
DescriptionВладелец - @bAPCNK_B_TAHKE Tейки - @jdmtakes_bot
CreatedBetween 1 February 2026 and 17 June 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live11 August 2026
Measurements held2
On Telegramt.me/jdm_cf

Growth

267 August 2026 — 26 subscribers11 August 2026 — 26 subscribers7 August 202611 August 2026
2 measurements spanning 4 days. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 25–27 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Aug 2026, 08:1926no change
7 Aug 2026, 19:1426first reading

Engagement

18 posts held, back to 17 June 2026the 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 18 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
77
Videos
8
Links
3

Lifetime counters from Telegram’s own channel header, read 11 August 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.

Video runtime
50s
Average length
17s

Measured directly from 3 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.

Reaction mix

162 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 41.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53282745154640524206741.4%
4225.9%
custom 52111873332436269142616.0%
❤‍🔥2012.3%
👍74.32%

Custom emoji. 2 of the rows above are 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 18 of the 18 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 162reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 17 June 2026 to 29 June 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.

Recent posts

29 Jun 2026, 06:28 UTC41 views9 reactionsread 11 August 2026
Photo

«———————————————————» •> #photo #post @jdm_cf

custom 521118733324362691442custom 53282745154640524202❤‍🔥1

29 Jun 2026, 01:58 UTC41 views9 reactionsread 11 August 2026
Video

«———————————————————» •> #video #post @jdm_cf

3custom 52111873332436269143❤‍🔥2custom 53282745154640524201

27 Jun 2026, 09:40 UTC23 views8 reactionsread 11 August 2026
Video

«———————————————————» •> #video #post @jdm_cf

3custom 52111873332436269142custom 53282745154640524202❤‍🔥1

26 Jun 2026, 02:44 UTC24 views10 reactionsread 11 August 2026
Photo

«———————————————————» •> #photo #post @jdm_cf

custom 532827451546405242052custom 52111873332436269142❤‍🔥1

25 Jun 2026, 02:38 UTC27 views11 reactionsread 11 August 2026
Photo

Nissan Silvia S15 1999-2002 Этот автомобиль считается одним из самых легендарных в JDM-культуре. У него был огромный потенциал для тюнинга, задний привод, легкая конструкция, поэтому он считается "королем дрифта". На нем до сих пор можно получить высокие успехи в дрифте. Самая мощная версия Spec-R оснащалась 2,0-литровым турбомотором, выдавал он 250 л.с ! Также в этой версии для 6 ступенчатая МКПП, модернизированна

custom 53282745154640524205custom 521118733324362691432❤‍🔥1

24 Jun 2026, 10:06 UTC23 views10 reactionsread 11 August 2026
Photo

«———————————————————» •> #photo #post @jdm_cf

custom 53282745154640524205❤‍🔥2custom 521118733324362691421

23 Jun 2026, 16:12 UTC24 views5 reactionsread 11 August 2026
Photo

«—————————————————————» •> #photo #post @jdm_cf

2custom 52111873332436269142custom 53282745154640524201

23 Jun 2026, 03:54 UTC28 views9 reactionsread 11 August 2026
Photo

«——————————————————» •> #photo #post @jdm_cf

custom 532827451546405242052custom 52111873332436269142

22 Jun 2026, 11:12 UTC27 views9 reactionsread 11 August 2026
Photo

«——————————————————» •> #photo #post @jdm_cf

3custom 53282745154640524203custom 52111873332436269142❤‍🔥1

22 Jun 2026, 04:46 UTC19 views10 reactionsread 11 August 2026
Photo

«——————————————————» •> #photo #post @jdm_cf

custom 532827451546405242052custom 52111873332436269142❤‍🔥1

21 Jun 2026, 10:31 UTC20 views11 reactionsread 11 August 2026
Photo

«———————————————————» •> #photo #post @jdm_cf

custom 532827451546405242072custom 52111873332436269142

21 Jun 2026, 08:09 UTC27 views9 reactionsread 11 August 2026
Photo

«——————————————————» •> #photo #post @jdm_cf

custom 53282745154640524205❤‍🔥21👍1

Showing the 12 most recent of 18 posts we hold for @jdm_cf. 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

Citation-graph rank — 1,038,104 of 1,160,990entries 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.

Forward network

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.

Mentions

Named by 1 registered channel — 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.

Named by

Channels on the register whose posts name this channel's handle.

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.

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 11 August 2026 — this entry's latest reading, not the date you are reading this.

“JDM confession 🚗🇯🇵” (@jdm_cf), 26 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/jdm_cf.

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.