Telegram RegisterThe public register of Telegram

Channel

Dragonlance TARO ZINE

@dragonlance_taro

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Handles named that no longer answer · Cite this entry

81subscribers

+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-1001938319971
TypeChannel
Username@dragonlance_taro
DescriptionТворческий проект по созданию колоды таро в сетинге вселенной DragonLance/Последнее Испытание в формате зина
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/dragonlance_taro

Growth

817 August 2026 — 81 subscribers9 August 2026 — 81 subscribers7 August 20269 August 2026
2 measurements spanning 3 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”. The vertical axis spans 80–82 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 18:3181no change
7 Aug 2026, 03:4581first reading

Engagement

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

What this channel posts

Photos
219
Links
138

Lifetime counters from Telegram’s own channel header, read 9 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

118 reactions across 11 posts, in 7 distinct kinds. The most used accounts for 44.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
5344.9%
❤‍🔥2722.9%
🔥1916.1%
🍓119.32%
🎄43.39%
🙏21.69%
🥰21.69%

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 12 of the 15 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 118reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 21 February 2024 to 12 May 2024, 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

12 May 2024, 13:32 UTC653 viewsread 9 August 2026
Forwarded from @ayyivaPoll

хотите?👀

  1. да81%
  2. нет3%
  3. не могу сказать16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

12 May 2024, 13:32 UTC652 views0 reactionsread 9 August 2026
Forwarded from @ayyiva

котюнчики, мы тут с риной подумали, похихикали и решили организовать мини-зин по драгонленсу, но это будет артбук с даламаром

8 Apr 2024, 09:42 UTC504 views10 reactionsread 9 August 2026
Photo

моя часть колоды @dragonlance_taro. напечатаны, расфасованы, распространены. круто. приятно. только вот как трактовать этот раскладик?

8🍓2

31 Mar 2024, 11:39 UTC668 views7 reactionsread 9 August 2026
Photo

⭐ РАСПРОДАЖА ОСТАТКОВ ⭐ Теперь для вас есть возможность докупить оставшийся мерч отдельно 🌙 Металлический пин - 500р (1200 за 3 шт) 🌙 Открытка А6 - 100р (300р за 4) 🌙 Колода карт Таро - 3000р Доступен самовывоз в Москве, а так же доставка почтой Для покупки пишите в личные сообщения @iiiuuuppp 🖤 ⭐ Все заказы будут разосланы в течении недели

🔥32🍓2

30 Mar 2024, 08:20 UTC415 views7 reactionsread 9 August 2026
Photo

⭐ПИНЫ У НАС ⭐ По поводу доставки и самовывоза свяжемся со всеми заказавшими в течении 1-2 дней

5🍓1🔥1

7 Mar 2024, 10:03 UTC428 views3 reactionsread 9 August 2026
Forwarded from @ayyivaPhoto

напоминаю что у меня открыты коммишки🩷 за репост буду очень благодарна и лично приеду поцелую в лоб прайс ❤по плечи/халф с полноценным рендером — 1000-1600 в зависимости от сложности, цветной скетч — 700 ❤полный рост рисую только цветной скетч с минимальным рендером — 800-1200 в завимимости от сложности ❤ч/б скетч любого формата — 600 детальный фон 500-1500 в зависимости от сложности, простой фон бесплатно н

🙏2🔥1

2 Mar 2024, 14:41 UTC≈1,030 views10 reactionsread 9 August 2026
Photo

🌙 Хорошие новости, у нас осталось 4 колоды! Которые можно приобрести, обратившись к @iiiuuuppp Стоимость колоды - 3 000 руб Возможна доставка почтой или самовывоз в Москве🖤 ⭐ Всем, чьи наборы задерживаются, мы положим небольшое подарочки за ожидание

10

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

12 May 2024, 13:32 UTCAnonymous Poll108 voters

хотите?👀

  1. да81%
  2. нет3%
  3. не могу сказать16%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 15 most recent posts we hold, published 21 February 2024 to 12 May 2024. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 364,686 of 1,345,403entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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.

Mentions

Names

Channels on the register whose handles appear in this channel's posts.

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

“Dragonlance TARO ZINE” (@dragonlance_taro), 81 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/dragonlance_taro.

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.