Telegram RegisterThe public register of Telegram
Telegram profile photo for Ивлев ШЕФ

Channel

Ивлев ШЕФ

@IvlevCheff

Verified by TelegramHas discussion group

On this record: Topic · Growth · Engagement · Citations · Cross-platform identity · Cite this entry

94,777subscribers

-840 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 31,623–100,000.

Register entry

Telegram ID-1001578479853
TypeChannel
Username@IvlevCheff
Created7 December 2021measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 August 2026
Last confirmed live11 September 2026
Measurements held31
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/IvlevCheff

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 21 August 2026 and assigned it the closest of 31 fixed categories, at 97% 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

94,77795,61795,1976 August 2026 — 95,617 subscribers6 August 2026 — 95,602 subscribers7 August 2026 — 95,582 subscribers8 August 2026 — 95,555 subscribers9 August 2026 — 95,547 subscribers10 August 2026 — 95,547 subscribers10 August 2026 — 95,531 subscribers11 August 2026 — 95,513 subscribers12 August 2026 — 95,493 subscribers14 August 2026 — 95,472 subscribers15 August 2026 — 95,436 subscribers17 August 2026 — 95,417 subscribers18 August 2026 — 95,409 subscribers19 August 2026 — 95,388 subscribers20 August 2026 — 95,352 subscribers21 August 2026 — 95,311 subscribers22 August 2026 — 95,270 subscribers24 August 2026 — 95,251 subscribers25 August 2026 — 95,239 subscribers26 August 2026 — 95,207 subscribers27 August 2026 — 95,194 subscribers28 August 2026 — 95,208 subscribers29 August 2026 — 95,150 subscribers30 August 2026 — 95,112 subscribers31 August 2026 — 95,086 subscribers1 September 2026 — 95,069 subscribers2 September 2026 — 95,038 subscribers3 September 2026 — 94,990 subscribers5 September 2026 — 94,946 subscribers8 September 2026 — 94,872 subscribers11 September 2026 — 94,777 subscribers6 August 202611 September 2026
31 measurements spanning 36 days, net -840. 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 94,651–95,743 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 31
Measured (UTC)SubscribersChange
11 Sept 2026, 06:4194,777-95
8 Sept 2026, 13:1794,872-74
5 Sept 2026, 05:3794,946-44
3 Sept 2026, 14:0294,990-48
2 Sept 2026, 08:3395,038-31
1 Sept 2026, 06:5695,069-17
31 Aug 2026, 07:3495,086-26
30 Aug 2026, 07:4895,112-38
29 Aug 2026, 08:2595,150-58
28 Aug 2026, 05:5695,208+14
27 Aug 2026, 06:3795,194-13
26 Aug 2026, 05:4995,207-32
25 Aug 2026, 07:1495,239-12
24 Aug 2026, 09:3795,251-19
22 Aug 2026, 14:3895,270-41
21 Aug 2026, 06:5395,311-41
20 Aug 2026, 08:1895,352-36
19 Aug 2026, 06:2395,388-21
18 Aug 2026, 07:2795,409-8
17 Aug 2026, 09:2695,417first reading

Engagement

No public post preview. We read this entry on 10 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

Named by 5 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.

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.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q4197202 on Wikidata, read 6 September 2026
LabelKonstantin Ivlev
DescriptionRussian chef
YouTubeUCRxH-Wdf4c_2nDu3_lIQrvg
Official sitehttps://www.ivlevgroup.com

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

“Ивлев ШЕФ” (@IvlevCheff), 94,777 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/IvlevCheff.

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.