Telegram RegisterThe public register of Telegram
Telegram profile photo for Firecup

Channel

Firecup

@firecup

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

1subscribers

+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-1001079180239
TypeChannel
Username@firecup
DescriptionУличные очаги Firecup все новинки тут
Created15 November 2016measured — dated from the channel’s first post
First recorded15 August 2026
Last confirmed live22 August 2026
Measurements held2
On Telegramt.me/firecup

Growth

17 August 2026 — 1 subscribers15 August 2026 — 1 subscribers7 August 202615 August 2026
2 measurements spanning 8 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Aug 2026, 01:011no change
7 Aug 2026, 11:541first reading

Engagement

5 posts held, back to 15 November 2016the 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 5 posts for this entry, the most recent from 11 May 2018. An engagement rate over an empty window would be a number about nothing.

Recent posts

8 May 2018, 01:26 UTC54 viewsread 15 August 2026
Forwarded from @TildaFormsBot

Данные заявки: Email: [email protected] Phone: +79214065694 Name: Юрий Дополнительные данные: Код заявки: 456056:9848644 Код блока: rec39320435 http://firecup.ru/page1943440.html -----

8 May 2018, 01:26 UTC55 viewsread 15 August 2026

Классический и мангал без топки

7 May 2018, 12:37 UTC55 viewsread 15 August 2026
Forwarded from @TildaFormsBot

Заказ #1263072818 Очаг УЮТНЫЙ: 17500 (1 x 17500)Цвет покрытия: Черный Сумма оплаты: 17500 р. Код платежа: не указана: 0 Данные плательщика: Name: Дмитрий Email: [email protected] Phone: 89857682824 Дополнительные данные: Код заявки: 456056:9584405 Код блока: rec38895843 Форма: Cart http://firecup.ru/firecups UTM source: google UTM medium: cpc UTM campaign: g UTM content: 258298380394 UTM term: +очаг +купить -----

Showing the 5 most recent of 5 posts we hold for @firecup. 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.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Firecup” (@firecup), 1 subscribers as measured 15 August 2026. Telegram Register, tgregister.com/channel/firecup.

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.