Telegram RegisterThe public register of Telegram
Telegram profile photo for ៸៸ Б𝗔ЗА Б𝗔НОВ. ५ ֺ 𝗗‌‌𝗞.

Channel

៸៸ Б𝗔ЗА Б𝗔НОВ. ५ ֺ 𝗗‌‌𝗞.

@base_DK

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

50subscribers

-2 since we began measuring on 11 August 2026

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

Register entry

Telegram ID-1002031823722
TypeChannel
Username@base_DK
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded11 August 2026
Last confirmed live31 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 31 August 2026
On Telegramt.me/base_DK

Growth

50525111 August 2026 — 52 subscribers11 August 2026 — 52 subscribers19 August 2026 — 51 subscribers25 August 2026 — 50 subscribers11 August 202625 August 2026
4 measurements spanning 14 days, net -2. 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 50–52 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 14:4850-1
19 Aug 2026, 00:4551-1
11 Aug 2026, 16:0052no change
11 Aug 2026, 15:4652first reading

Engagement

20 posts held, back to 9 February 2025the 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 31 October 2025. An engagement rate over an empty window would be a number about nothing.

Recent posts

31 Oct 2025, 03:35 UTC181 viewsread 11 August 2026

Причина бана: реклама сомнительных услуг ID: 1838944256 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖

3 Oct 2025, 16:42 UTC218 viewsread 11 August 2026

Причина бана: копирование чужих работ ID: 7230562883 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖

26 Sept 2025, 18:29 UTC192 viewsread 11 August 2026

Причина бана: копирование чужих работ ID: 7251922639 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖ n͟͟o͟͟t͟͟ a͟͟ d͟͟e͟͟s͟͟i͟͟g͟͟n͟͟e͟͟r͟͟ ! @DK_

16 Sept 2025, 08:52 UTC182 viewsread 11 August 2026

Причина бана: Реклама сомнительных услуг ID: 6647549652 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖ n͟͟o͟͟t͟͟ a͟͟ d͟͟e͟͟s͟͟i͟͟g͟͟n͟͟e͟͟r͟͟ !

15 Sept 2025, 11:38 UTC160 viewsread 11 August 2026

Причина бана: Реклама сомнительных услуг ID: 756750011 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖ n͟͟o͟͟t͟͟ a͟͟ d͟͟e͟͟s͟͟i͟͟g͟͟n͟͟e͟͟r͟͟ !

15 Sept 2025, 08:46 UTC129 viewsread 11 August 2026

Причина бана: Реклама сомнительных услуг ID: 1539675468 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖ n͟͟o͟͟t͟͟ a͟͟ d͟͟e͟͟s͟͟i͟͟g͟͟n͟͟e͟͟r͟͟ !

13 Sept 2025, 18:09 UTC120 viewsread 11 August 2026

Причина бана: Скам ID: 6349765577 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖ n͟͟o͟͟t͟͟ a͟͟ d͟͟e͟͟s͟͟i͟͟g͟͟n͟͟e͟͟r͟͟ !

13 Sept 2025, 06:29 UTC114 viewsread 11 August 2026

Причина бана: сомнительные услуги ID: 8010681423 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖ n͟͟o͟͟t͟͟ a͟͟ d͟͟e͟͟s͟͟i͟͟g͟͟n͟͟e͟͟r͟͟ !

12 Sept 2025, 13:17 UTC113 viewsread 11 August 2026

Причина бана: Попытка Скама ID: 5704286328 Открыть пруфы

Signed 𖥔˖ ࣪ ℳ𝑒𝑙ꪮ𝑑𝑦 ! ៹ ࣪˖ n͟͟o͟͟t͟͟ a͟͟ d͟͟e͟͟s͟͟i͟͟g͟͟n͟͟e͟͟r͟͟ !

14 Jun 2025, 09:24 UTC186 viewsread 11 August 2026

Причина бана: Реклама без разрешения администрации. ID: 5071530408 Открыть пруфы.

Signed ꒰ 𐌗ᥙρ᧐ ꒱ #love ოe

10 May 2025, 05:55 UTC225 viewsread 11 August 2026

Причина бана: несанкционированная реклама. ID: 1549125450 Открыть пруфы.

Signed 𝗁𝗈𝗏𝖺

30 Mar 2025, 09:09 UTC206 viewsread 11 August 2026

Причина бана: полное копирование чужой работы. ID: 7294091559 Открыть пруфы.

Signed 𝗁𝗈𝗏𝖺

Showing the 12 most recent of 20 posts we hold for @base_DK. 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“៸៸ Б𝗔ЗА Б𝗔НОВ. ५ ֺ 𝗗‌‌𝗞.” (@base_DK), 50 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/base_DK.

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.