Telegram RegisterThe public register of Telegram
Telegram profile photo for d_nicolaev

Channel

d_nicolaev

@d_nicolaev

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

18,132subscribers

+207 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001582450620
TypeChannel
Username@d_nicolaev
CreatedBetween 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded17 August 2026
Last confirmed live18 September 2026
Measurements held27
Confirmed unchanged1 time, most recently 18 September 2026
On Telegramt.me/d_nicolaev

Topic

Other / unclassifiable — 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 10 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

17,92518,13218,028.57 August 2026 — 17,925 subscribers8 August 2026 — 17,927 subscribers9 August 2026 — 17,929 subscribers11 August 2026 — 17,931 subscribers12 August 2026 — 17,934 subscribers14 August 2026 — 17,939 subscribers15 August 2026 — 17,943 subscribers17 August 2026 — 17,947 subscribers17 August 2026 — 17,947 subscribers18 August 2026 — 17,951 subscribers19 August 2026 — 17,954 subscribers20 August 2026 — 17,951 subscribers22 August 2026 — 17,954 subscribers24 August 2026 — 17,957 subscribers25 August 2026 — 17,960 subscribers28 August 2026 — 17,962 subscribers30 August 2026 — 17,964 subscribers31 August 2026 — 17,965 subscribers31 August 2026 — 17,962 subscribers3 September 2026 — 17,961 subscribers4 September 2026 — 17,963 subscribers7 September 2026 — 17,971 subscribers10 September 2026 — 17,992 subscribers12 September 2026 — 17,988 subscribers14 September 2026 — 18,000 subscribers16 September 2026 — 18,052 subscribers18 September 2026 — 18,132 subscribers7 August 202618 September 2026
27 measurements spanning 41 days, net +207. 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 17,894–18,163 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 27
Measured (UTC)SubscribersChange
18 Sept 2026, 03:3618,132+80
16 Sept 2026, 00:4018,052+52
14 Sept 2026, 05:3918,000+12
12 Sept 2026, 16:2017,988-4
10 Sept 2026, 17:5717,992+21
7 Sept 2026, 14:5717,971+8
4 Sept 2026, 13:5717,963+2
3 Sept 2026, 04:1417,961-1
31 Aug 2026, 23:1817,962-3
31 Aug 2026, 01:4317,965+1
30 Aug 2026, 05:0317,964+2
28 Aug 2026, 02:5617,962+2
25 Aug 2026, 06:4217,960+3
24 Aug 2026, 08:4717,957+3
22 Aug 2026, 13:2917,954+3
20 Aug 2026, 07:3517,951-3
19 Aug 2026, 06:3417,954+3
18 Aug 2026, 08:0217,951+4
17 Aug 2026, 16:2717,947no change
17 Aug 2026, 10:0617,947first reading

Engagement

No public post preview. We read this entry on 17 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Stom Journal | Стоматология
@stom_journal · 24,733
Telegram ranks this channel #11 of 83 here — alongside 82 others — read 15 September 2026
Dentist
@dentistinfo · 22,156
Telegram ranks this channel #19 of 73 here — alongside 72 others — read 21 September 2026
Dental videos | Стоматологические видео | Стоматология
@stom_video · 31,002
Telegram ranks this channel #19 of 78 here — alongside 77 others — read 6 September 2026
Книги по стоматологии | Dental books | Стоматология
@stomkniga · 42,672
Telegram ranks this channel #19 of 81 here — alongside 80 others — read 6 September 2026
Терапевтическая и Эстетическая стоматология | Endodontia and Apical Surgery
@stom_ter · 31,403
Telegram ranks this channel #20 of 80 here — alongside 79 others — read 6 September 2026
Научная стоматология | Dental science
@sciencedent · 22,820
Telegram ranks this channel #22 of 79 here — alongside 78 others — read 19 September 2026
Стоматология | Dentistry
@rznstom · 41,838
Telegram ranks this channel #41 of 83 here — alongside 82 others — read 6 September 2026

This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“d_nicolaev” (@d_nicolaev), 18,132 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/d_nicolaev.

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.