Telegram RegisterThe public register of Telegram
Telegram profile photo for Remote Full-Stack Jobs

Channel

Remote Full-Stack Jobs

@findmyremote_fullstack

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

633subscribers

+20 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-1001924593974
TypeChannel
Username@findmyremote_fullstack
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/findmyremote_fullstack

Growth

6136336237 August 2026 — 613 subscribers8 August 2026 — 613 subscribers15 August 2026 — 617 subscribers23 August 2026 — 633 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net +20. 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 610–636 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 00:44633+16
15 Aug 2026, 05:34617+4
8 Aug 2026, 03:03613no change
7 Aug 2026, 11:47613first reading

Engagement

20 posts held, back to 19 July 2026the 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.

ERR · 30 days
8.77%
avg views ÷ 633 subscribers
Avg views / post
55.5
15 posts measured
Reaction rate
2.24%
reactions ÷ views · ER floor
Posts in window
15
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 2 of 15 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (19 July 20267 August 2026)
Views total833
Reactions total3
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 03:03 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

4 reactions across 3 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍4100.0%

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 3 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 4reactions 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 19 July 2026 to 7 August 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

7 Aug 2026, 08:00 UTC30 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Java / Angular Developer @ Jobgether 🗓️ Posted: 05 Aug 2026 💼 Employment: Contract 📍 Locations: 🇮🇳 India Lead Full Stack Developer @ Jobgether 🗓️ Posted: 31 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇮🇳 India Senior Full-Stack Engineer @ Jobgether 🗓️ Posted: 31 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇪🇸 Spain Software Engineer –

6 Aug 2026, 08:00 UTC39 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Software Craftsperson/Java/Angular @ Jobgether 🗓️ Posted: 04 Aug 2026 💼 Employment: Full-time 📍 Locations: 🇫🇷 France WordPress WooCommerce Full-Stack Developer @ Jobgether 🗓️ Posted: 31 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇮🇪 Ireland Senior Full-Stack Software Engineer, Community Building @ Acorns 🗓️ Posted: 04 Aug 2026 💼 Employme

5 Aug 2026, 08:00 UTC47 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Senior Full Stack Engineer .NET / React (554) @ Ubiminds: You, International. 🗓️ Posted: 03 Aug 2026 💼 Employment: Full-time Senior Software Engineer – .NET / Angular (555) @ Ubiminds: You, International. 🗓️ Posted: 03 Aug 2026 💼 Employment: Full-time Desenvolvedor de Sistemas | Fullstack | Java e React | Sistemas 1 | Crédito 3 | Cresol Co

4 Aug 2026, 08:00 UTC61 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Senior Fullstack Mobile Engineer @ Fundraise Up 🗓️ Posted: 03 Aug 2026 📍 Locations: 🇵🇱 Poland Senior Full Stack Developer @ Codekeeper 🗓️ Posted: 03 Aug 2026 Senior Full Stack Software Developer @ Outsourcing Advantage 🗓️ Posted: 03 Aug 2026 📍 Locations: 🇵🇭 Philippines, 🇩🇴 Dominican Republic, 🇨🇴 Colombia, 🇪🇬 Egypt, 🇧🇷 Brazil + 1 more Hiri

3 Aug 2026, 08:00 UTC50 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Senior Full-Stack Lead Developer @ Nile Bits 🗓️ Posted: 02 Aug 2026 💼 Employment: Full-time 📍 Locations: 🇪🇬 Egypt Senior Full-Stack Engineer @ Jobgether 🗓️ Posted: 31 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇩🇪 Germany Manager, Software Engineering, Fullstack (Repayment UX Engineering) @ Affirm 🗓️ Posted: 30 Jul 2026 📍 Locations: 🇪🇸 S

2 Aug 2026, 08:00 UTC55 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Software Engineer II (Fullstack) @ Jobgether 🗓️ Posted: 29 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇮🇳 India Senior Fullstack Engineer @ Spotify 🗓️ Posted: 31 Jul 2026 💼 Employment: Contract Senior Full Stack Engineer @ Agile Defense 🗓️ Posted: 31 Jul 2026 WordPress WooCommerce Full-Stack Developer @ Jobgether 🗓️ Posted: 31 Jul 2026

1 Aug 2026, 08:00 UTC48 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Member of Engineering (Interfaces, Full Stack) @ Jobgether 🗓️ Posted: 29 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇨🇭 Switzerland Senior Full Stack Software Engineer @ Jobgether 🗓️ Posted: 28 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇩🇪 Germany Full Stack Software Engineer @ New Era Technology 🗓️ Posted: 31 Jul 2026 Senior FullSta

31 Jul 2026, 08:00 UTC64 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Full stack Developer @ Sparksoft Corporation 🗓️ Posted: 30 Jul 2026 Senior Fullstack Product Software Engineer, Web Experience @ Dropbox 🗓️ Posted: 30 Jul 2026 Senior Full Stack Engineer @ Pavago 🗓️ Posted: 28 Jul 2026 📍 Locations: 🇯🇲 Jamaica, 🇵🇦 Panama, 🇸🇻 El Salvador, 🇭🇳 Honduras, 🇧🇿 Belize Senior Full-Stack Engineer, Contract @ Xcelira

30 Jul 2026, 08:00 UTC60 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Senior Full-Stack Developer with DevOps (International Hiring) @ ERNI Philippines 🗓️ Posted: 29 Jul 2026 📍 Locations: 🇵🇭 Philippines Senior Full Stack Engineer @ Pavago 🗓️ Posted: 28 Jul 2026 📍 Locations: 🇨🇴 Colombia, 🇧🇷 Brazil, 🇲🇽 Mexico, 🇦🇷 Argentina, 🇨🇷 Costa Rica Senior Software Engineer - Full Stack - Customer Experience Team @ Nir Yu

29 Jul 2026, 08:00 UTC62 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Senior Software Engineer, Full-Stack - Security Platform @ Vannevar Labs 🗓️ Posted: 27 Jul 2026 Software Development Engineer SR -Full Stack Java/React @ Sagent 🗓️ Posted: 27 Jul 2026 Senior Software Engineer (Fullstack) @ Sophos 🗓️ Posted: 28 Jul 2026 💼 Employment: Contract 📍 Locations: 🇮🇳 India Desenvolvedor Full Stack - PJ (Home Office

28 Jul 2026, 08:00 UTC59 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Lead Full Stack Engineer (.Net, Vue/React) - Hybrid/Fully Remote @ CoverGo 🗓️ Posted: 27 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇻🇳 Vietnam Engineer II, Full Stack @ Bellese 🗓️ Posted: 27 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇺🇸 United States Shopify Full Stack Developer @ Jobgether 🗓️ Posted: 27 Jul 2026 💼 Employment: Contra

27 Jul 2026, 08:00 UTC60 viewsread 8 August 2026

Hey job seekers! Check out a handful of remote full-stack roles (15 found)! Senior Full Stack Engineer @ webAI 🗓️ Posted: 22 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇺🇸 United States Senior Full Stack Engineer @ webAI 🗓️ Posted: 22 Jul 2026 💼 Employment: Full-time 📍 Locations: 🇺🇸 United States Senior Software Engineer (Full Stack) - Raise @ Virtuous 🗓️ Posted: 22 Jul 2026 💼 Employment: Full-time 📍 Locations:

Showing the 12 most recent of 20 posts we hold for @findmyremote_fullstack. 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 — 206,386 of 1,584,142entries 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.

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.

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

“Remote Full-Stack Jobs” (@findmyremote_fullstack), 633 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/findmyremote_fullstack.

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.