Telegram RegisterThe public register of Telegram

Channel

evancoric

@evancoric

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

235subscribers

+0 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001660593272
TypeChannel
Username@evancoric
Descriptionhello… 🪑🚪 boosty.to/puzzlecda
CreatedBetween 1 December 2021 and 31 March 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live7 August 2026
Measurements held2
On Telegramt.me/evancoric

Growth

2356 Aug 2026, 09:38 — 235 subscribers7 Aug 2026, 02:46 — 235 subscribers6 Aug 2026, 09:387 Aug 2026, 02:46
2 measurements taken within a single day. 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 234–236 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Aug 2026, 02:46235no change
6 Aug 2026, 09:38235first reading

Engagement

15 posts held, back to 18 March 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 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 24 April 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
20
Videos
10
Links
6

Lifetime counters from Telegram’s own channel header, read 7 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

229 reactions across 13 posts, in 7 distinct kinds. The most used accounts for 45.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 540261931273108139010345.0%
custom 52941698680886772434921.4%
custom 54180140517729419622912.7%
custom 52065754746706047952711.8%
custom 5460995778073878012135.68%
custom 521535830483380185152.18%
custom 529422580144776789031.31%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 13 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 229reactions 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 18 March 2025 to 24 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

24 Apr 2026, 06:20 UTC606 views25 reactionsread 7 August 2026
Video

ICEMAN TEASER for @champagnepapi (CONCEPT WORK) 15.05.26 Creative Direction — @evancoric AI Artist — @suzuyvibes AI Artist — @evancoric AI Artist — @nfkFM23 Edit — @evancoric ICEMAN CORP LLC

custom 529416986808867724310custom 54026193127310813908custom 52065754746706047957

21 Apr 2026, 07:08 UTC562 views18 reactionsread 7 August 2026
Video

Video, posted without a caption

custom 52941698680886772439custom 52065754746706047954custom 54026193127310813904custom 52942258014477678901

21 Apr 2026, 07:08 UTC512 views17 reactionsread 7 August 2026
Video

Video, posted without a caption

custom 52941698680886772438custom 54026193127310813904custom 52065754746706047953custom 52942258014477678902

20 Apr 2026, 18:17 UTC489 views13 reactionsread 7 August 2026
Video

“WORKFLOW”

custom 54026193127310813909custom 52065754746706047952custom 52941698680886772432

20 Apr 2026, 06:57 UTC484 views27 reactionsread 7 August 2026
Video

"Where time stands still forever" AI FOR VACHERON CONSTANTIN (CONCEPT ANIMATION) evancoric.com

custom 540261931273108139015custom 52941698680886772437custom 52065754746706047955

20 Apr 2026, 00:58 UTC414 views16 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 54026193127310813907custom 52153583048338018515custom 52941698680886772434

17 Apr 2026, 17:57 UTC455 views20 reactionsread 7 August 2026

Не видел места лучше чем DevTown. 🧩🧩🧩🧩🧩🧩 🧩🧩🧩🧩🧩🧩 🧩🧩🧩🧩🧩🧩 🧩🧩🧩🧩🧩🧩 🧩🧩🧩🧩🧩🧩 🧩🧩🧩🧩🧩🧩 🧩🧩🧩🧩🧩🧩 Сделали так много пикселей что картинка стала объемной.

custom 52941698680886772439custom 52065754746706047956custom 54026193127310813905

1 Nov 2025, 13:59 UTC≈1,350 views21 reactionsread 7 August 2026
Photo

Photo, posted without a caption

custom 541801405177294196212custom 54609957780738780128custom 54026193127310813901

31 Oct 2025, 08:14 UTC≈1,260 views26 reactionsread 7 August 2026
Forwarded from @dddenkoPhoto

ЭЛДЖЕЙ & ANIKV stage visual CG: @dddenko @evancoric @barsbektur Edit & compositing: @someoneornikitos Production: Showrun

custom 540261931273108139016custom 54180140517729419625custom 54609957780738780125

20 Jul 2025, 11:23 UTC≈2,130 views15 reactionsread 7 August 2026
Video

@kaicenat & @rayasianboy_ — «Ray Gets His Visa» Director: @chrisvilla Director of Photography: @john_matysiak Editor: @matthewvietzke Colorist: @waltervolpatto Sound Design: @ayodouson Music & Score: @mic_ferrante15 Visual Effects: @BiohazardVFX Post Producer: @davaneh VFX Supervisor: @nicholai.exe Head of Production: @nuke_fx Prep Lead: @tanvirhc1 Compositors: @ideas.re.bulletproof, @tenebrismethod, @benvmorse, @

custom 54026193127310813909custom 54180140517729419626

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

Citation-graph rank

Citation-graph rank — 630,340 of 1,151,006entries 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

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

Named by 4 registered channels — 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.

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

“evancoric” (@evancoric), 235 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/evancoric.

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.