Telegram RegisterThe public register of Telegram
Telegram profile photo for Tajirs.

Channel

Tajirs.

@Tajirs

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

63subscribers

-3 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1001569103190
TypeChannel
Username@Tajirs
CreatedBetween 1 August 2021 and 10 August 2022 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live9 September 2026
Measurements held4
Confirmed unchanged1 time, most recently 9 September 2026
On Telegramt.me/Tajirs

Growth

636664.59 August 2026 — 66 subscribers10 August 2026 — 66 subscribers17 August 2026 — 64 subscribers9 September 2026 — 63 subscribers9 August 20269 September 2026
4 measurements spanning 31 days, net -3. 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 63–66 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Sept 2026, 13:3963-1
17 Aug 2026, 12:2364-2
10 Aug 2026, 02:0366no change
9 Aug 2026, 17:3066first reading

Engagement

20 posts held, back to 10 August 2022the 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 17 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
5s
Average length
5s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

258 reactions across 8 posts, in 18 distinct kinds. The most used accounts for 32.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🎉8432.6%
🦄2710.5%
238.91%
🆒176.59%
❤‍🔥155.81%
👍145.43%
🕊124.65%
🤩114.26%
👏103.88%
💘93.49%
🐳83.10%
💋72.71%
🏆51.94%
🥰51.94%
💯41.55%
😘41.55%
🍓20.775%
😍10.388%

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

Measured over the 20 most recent posts we hold, published 10 August 2022 to 17 April 2026, 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

23 Jul 2023, 03:54 UTC811 views37 reactionsread 10 August 2026
Photo

• 1998’s PHASE ON THIS TROPS. Towards enterily mate, Mutual purpose could knock this one @tajirsbot. Acquire a sense of enchantement in the concept of sorely. I do amongst see in that way, regardless of physical magnanimous: Chatter—Box towards Asking something aforementioned username, @tajirsbot.

🆒75❤‍🔥4🐳4🤩4🎉3🦄3😘3

23 Jul 2023, 03:47 UTC681 views16 reactionsread 10 August 2026
Photo

“Thee merely experience what actually happens once. This allows a recurring freshness of discovery what lone imagines shall certainly happen a second furthermore third chronology. Until one breaks out from the portrait. Nevertheless it must be approximating oranges which not only give pleasure but also freshness. Sincerely gratitude, bestowed to you! Acquire a blissful astronomical daylight enterily cherised.”

💋4🏆2🕊2🦄2🆒2👍1👏1🥰1

23 Jul 2023, 03:45 UTC496 views17 reactionsread 10 August 2026
Photo

“They was lone of those populance which are usually referred to in the boundary tense, of whom lone conveys: 'they had a certain freshness and bloom aformentioned,' furthermore whose freshness amongst bloom passed unnoticed evenmore when they still had effective practice of solitude always give birth to freshness renewal refocus, rejuvenation revelation and restoration.”

❤‍🔥4💘4🆒3🎉21💯1🤩1🦄1

23 Jul 2023, 03:44 UTC402 views14 reactionsread 10 August 2026
Photo

“As gloom furthermore doom acquire been creeping towards their sentiences, abundant couldn’t auxiliary anymore the freshness of their boisterous that withered alongside the wearisome path of their expectations. Peace is a adolescence picturesque smile amongst a florescence freshness peace is an inner perception of joyfulness and eudomonia.”

🕊32❤‍🔥2🆒2🏆1👏1💋1💘1

23 Jul 2023, 03:39 UTC348 views37 reactionsread 10 August 2026
Photo

“Even so, yonder were chronologys I saw freshness furthermore pulchritudinous. I could smell the air, amongst I really loved rock 'n' roll. Tears were warm amidst personage were magnanimous, approximating dreams. I approximatinged monograph theaters, the darkness nd’ intimacy, and I approximatinged the deep melancholy summer eventides.”

🦄21🎉4🤩3🐳2💯2🕊2❤‍🔥1💋1

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

3 Apr 2023, 04:21 UTCAnonymous Poll97 voters

siapa setuju Tajirs reborn?

  1. Me63%
  2. Aku37%

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 20 most recent posts we hold, published 10 August 2022 to 17 April 2026. 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.

Forward network

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

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

“Tajirs.” (@Tajirs), 63 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/Tajirs.

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.