Channel
@bicc_exchange
On this record: Topic · Growth · Engagement · Posts · Telegram's recommendations · Cite this entry
1,385subscribers
+12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001250958404 |
|---|---|
| Type | Channel |
| Username | @bicc_exchange |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 2 times, most recently 15 September 2026 |
| On Telegram | t.me/bicc_exchange |
Job listings — 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 17 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 04:42 | 1,385 | +4 |
| 7 Sept 2026, 20:58 | 1,381 | -2 |
| 2 Sept 2026, 21:14 | 1,383 | +3 |
| 30 Aug 2026, 13:03 | 1,380 | -4 |
| 27 Aug 2026, 07:58 | 1,384 | +4 |
| 24 Aug 2026, 13:37 | 1,380 | +1 |
| 20 Aug 2026, 18:23 | 1,379 | +2 |
| 18 Aug 2026, 00:43 | 1,377 | +4 |
| 7 Aug 2026, 22:19 | 1,373 | no change |
| 7 Aug 2026, 14:18 | 1,373 | first reading |
20 posts held, back to 24 July 2026 — the 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 7 August 2026. An engagement rate over an empty window would be a number about nothing.
#lookfor 🔎Full-Stack Engineer Grade: Senior Stack: TypeScript, Node.js (Express), PostgreSQL, Svelte, React, GCP. Small team, real customers, real revenue. English level: B2+ Requirements: - Hands-on experience with financial tools - QuickBooks (must-have). - Strong background in Node.js, TypeScript, PostgreSQL, and React + Svelte. - Deep experience with REST APIs (QuickBooks, Stripe, HubSpot, similar). - Backgr…
#lookfor #outstaff #fulltime 🔎Flutter Developer Requirements: Важно уметь не просто писать код, а выстраивать диалог с заказчиком, аргументировать решения и быстро находить общий язык в международной команде. English level: B2+ (fluent) Start: ASAP Contact: @YanaSokal
#available #outstaff #qa #mqa 📇QA Engineers (2) 🧑🏻💻Grade: Senior Experience: 7+ years in FinTech, Healthcare, Logistics, and Automotive web apps. Skilled in end-to-end QA and leveraging AI to accelerate testing and defect analysis for high-quality product delivery English level: B2 🧑🏻💻Grade: Middle Experience: 4+ years ensuring quality for high-scale AWS/Salesforce e-commerce platforms. Expert in API (Postman, G…
#devops #devsecops #ml #available #outstaff #remote 📇DevSecOps Engineer Experience: DevOps with a strong focus on security practices 📇DevOps Engineer Experience: in ML projects English level: B2+ (fluent) Contact: @happy_2b_kot
#lookfor 🔎React developer Requirements: with experience with Capacitor. Need a help in publishing existing web application to the Apple App Store and Google Play Stack: React TypeScript Supabase TanStack Start Tailwind CSS Capacitor Contact: @anastasiya_hol
#lookfor 🔎SSIS / MS SQL Server Developer (Data Warehouse Support & Maintenance) Requirements: Looking for an Expert-level SSIS Developer with strong MS SQL Server experience Expert SSIS — able to read, debug, and modify existing SSIS packages from day one Strong T-SQL, stored procedures, query/performance troubleshooting Experience supporting on-prem SQL Server Data Warehouses ETL, dimensional models, job schedulin…
#available #FrontendEngineer #outstaff #remote 📇React/TypeScript/Node.js Developer Grade: Senior Experience: 6+ лет English level: C1 Stack: React.js, Redux, Next.js, TypeScript, JavaScript, Node.js, GraphQL, React Native, Material UI, Ant Design, PostgreSQL, MongoDB, Docker, Kubernetes Start: in the near future Contact: @yuliya_wellnuts
#available #react #node #nest #angular #fullstack #qt #kotlin #swift 📇Backend Engineer Stack: NestJS, Node.js Experience: 5 years 📇Frontend Engineer Stack: Angular, React Experience: 5 years 📇Full-stack Engineer Stack: Angular, NestJS, Node.js, React, React Native Experience: 12 years 📇Mobile Engineer Stack: Kotlin, IQAN, Swift, Java Experience: 5 years 📇Solution Architect/ Backend Engineer Stack: NestJS, Node.j…
#available #outstaff #remote 📇Ruby on Rails developers 📇Java developers 📇PHP developers 📇QA/AQA engineers 📇Node/React developers 📇DevOps engineers 📇UI/UX product designers Contact: @bdm_twinslash
#lookfor 🔎Full-Stack Engineer Grade: senior/lead English level: B2 (min) Stack: python/next.js Duration: 2 мес. Contact: @TaniaSc
#available #ProductManager 📇Product Manager Experience: with a B2C and Fintech background. Especially interested in opportunities at the intersection of Fintech and AI Her primary focus is B2C products, particularly in Fintech, where she is passionate about optimizing digital payment journeys, onboarding flows, user engagement, and overall product experience. She is especially interested in opportunities at the int…
#lookfor 🔎Full-Stack Developer (React Python) backend oriented Grade: Senior Requirements: - Full-stack development, with experience building and delivering full-stack end-to-end projects - Leveraging AI APIs, vector search, RAG - Frontend Technologies (Vue, Typescript, Javascript, React) - Backend Technologies (Python) - Database Management (Postgres, SQL, NoSQL) - Understands API integrations and backend design …
Showing the 12 most recent of 20 posts we hold for @bicc_exchange. 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.
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.
This channel appears in 3 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“BICC International: Bench Exchange” (@bicc_exchange), 1,385 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/bicc_exchange.
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.