Telegram RegisterThe public register of Telegram
Telegram profile photo for В гостях у Торгаша 2.0

Channel

В гостях у Торгаша 2.0

@cheapjackshous

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

446subscribers

-8 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-1001454185017
TypeChannel
Username@cheapjackshous
Created27 April 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded8 August 2026
Last confirmed live11 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/cheapjackshous

Topic

Literature — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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 why it has no browse page of its own yet.

Growth

4464544507 August 2026 — 454 subscribers8 August 2026 — 454 subscribers16 August 2026 — 452 subscribers31 August 2026 — 451 subscribers9 September 2026 — 448 subscribers17 September 2026 — 447 subscribers1 October 2026 — 448 subscribers11 October 2026 — 446 subscribers7 August 202611 October 2026
8 measurements spanning 65 days, net -8. 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 445–455 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 07:02446-2
1 Oct 2026, 14:55448+1
17 Sept 2026, 07:55447-1
9 Sept 2026, 22:01448-3
31 Aug 2026, 07:47451-1
16 Aug 2026, 19:54452-2
8 Aug 2026, 05:00454no change
7 Aug 2026, 15:46454first reading

Engagement

20 posts held, back to 2 May 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 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

103 reactions across 19 posts, in 8 distinct kinds. The most used accounts for 46.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤4846.6%
🔥2827.2%
😢109.71%
🤯76.80%
😁32.91%
🥰32.91%
👀21.94%
🤔21.94%

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 103 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 2 May 2026 to 5 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.

Recent posts

5 Aug 2026, 19:50 UTC32 views10 reactionsread 8 August 2026
Photo

Что то я давно не рисовала батю года, спустя 3 года дошли руки до полноценки

🔥10

30 Jul 2026, 07:51 UTC57 views4 reactionsread 8 August 2026

Если что, 109 глава уже на Фикбуке

❤4

29 Jul 2026, 23:10 UTC59 views4 reactionsread 8 August 2026

Сижу, редактирую главу, уже почти все готово, думаю запустить промо. Извините, а фикбук не охуел случаем, почему мне никто не сказал, что промо теперь 700 монеток. 700 блять!

😢4

24 Jul 2026, 21:43 UTC87 views4 reactionsread 8 August 2026
Photo

Сижу на даче без света. На заброшенном участке дерево руинит проводку, поэтому периодически выбивает рубильник на трансформаторе. Ремонтная бригада заебалась, оставила трансформатор открытым и сказала при каждом отключении включать рубильник самостоятельно. Я может блять чего-то не понимаю, но по-моему, сука, нас всех в школе учили не лезть в ебучую трансформаторную будку

🤯4

13 Jul 2026, 19:56 UTC107 views8 reactionsread 8 August 2026

Я купила серую толстовку, вопрос к экспертам. Когда появится альфа мультимиллиардовый миллиардер, который закроет мои долги?

😢6🔥2

28 Jun 2026, 22:55 UTC125 views9 reactionsread 8 August 2026
Photo

Скетч огонь, молимся чтобы и покрас вышел

❤9

3 Jun 2026, 17:32 UTC160 views11 reactionsread 8 August 2026
Photo

Омагад эоо что? Это иллюстрация к фанфику на которую я потратила ГОД

🔥11

1 Jun 2026, 07:26 UTC102 views4 reactionsread 8 August 2026
Photo

Хоба, вот и месяц гордости, надеюсь, меня не посадят

🤯3❤1

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

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

“В гостях у Торгаша 2.0” (@cheapjackshous), 446 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/cheapjackshous.

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.