ICECCS

International Conference on Engineering of Complex Computer Systems

Editions listed12 Covered2012–2026 Rank nowCORE B ProceedingsPaywalled

Editions

Year	Ed.	Held	Where	Paper deadline	Accepted	Rate
2026	30	23–24 Nov 2026	Brisbane 🇦🇺	20 Jul +14 days	—	—
2025	29	2–4 Jul 2025	Hangzhou 🇨🇳	11 Feb +7 days	—	—
2024	28	19–21 Jun 2024	St. Raphael Resort and Marina 🇨🇾	5 Jan +21 days	—	—
2023	27	12–16 Jun 2023	Toulouse 🇫🇷	16 Jan +32 days	22 / 52	42%
2021, 2022 — not recorded here, which does not mean the conference did not meet
2020	25	28–31 Oct 2020	Online	10 Jun +12 days	—	—
2019	24	10–13 Nov 2019	Hong Kong 🇭🇰	14 Jun +14 days	—	—
2018	23	12–14 Dec 2018	Melbourne 🇦🇺	1 Jul +9 days	—	—
2017	22	5–8 Nov 2017	Fukuoka 🇯🇵	3 Jul +14 days	—	—
2016	21	6–8 Nov 2016	Dubai 🇦🇪	16 Jul +19 days	—	—
2015	20	9–12 Dec 2015	Gold Coast 🇦🇺	5 Jul +14 days	—	—
2014	19	4–7 Aug 2014	Tianjin 🇨🇳	14 Mar	—	46%
2013 — not recorded here, which does not mean the conference did not meet
2012	—		—	—	37 / 128	29%

A missing year does not mean the conference did not meet: coverage before 2012 has not been verified.

Acceptance rate over time

0%30%60%

2023 42% 22/52
2014 46%
2012 29% 37/128

Scale runs to 60%; the mid-line marks 30%. No figure published for 2015, 2016, 2017, 2018, 2019, 2020, 2024, 2025, 2026.

Submissions

2023 52
2012 128

Scaled to this conference's own busiest year (128), so the shape is comparable across its editions but not between conferences.

How it has reviewed and published

Practice	14	15	16	17	18	19	20	23	24	25	26
Proceedings	•	•	•	•	•	•	•	•	•	•	•
Anonymity											S

Practice

Proceedings

•

Anonymity

A blank cell means nobody has checked that year, not that the answer is no. Licences are read as recorded on the edition, never inherited from the publisher.

Where it has met

Loads tiles from OpenStreetMap, which will see your IP address.

10 cities. 20142026

10 cities, 7 countries, 3 continents. Met online 1 time.

CORE rank over time

A 2015–2022 B 2023–

Ranks before 2015 are unknown.

Timing

Closes: anywhere between 20 Jul and 14 Jun, over the last 6 editions.
Decision: 52 days after the deadline (23–70 over 11 editions)
Then: 94 days to the conference (83–113)

No call is open. If it runs again and keeps to its habits, expect the next one to close somewhere in that range — but that is this page reading a pattern, not an announcement.

Deadline habits

Extended: 10 of 10 editions
Typical: 7–32 days
Longest: 32 days
Not known: 1 edition

An edition counts as firm only when it was checked; a deadline with no earlier date recorded is counted as not known, not as firm.

Elsewhere

DBLP: iceccs ↗
CORE: portal entry 646 ↗
Calendar: Subscribe to ICECCS
Data: All editions as JSON

Notes carried over

Acceptance: 29% (37/128) in 2012, 45% (21 full + 15 short / 80) in 2013, 46% in 2014 (17 full + 12 short / 62, with an acceptance rate of 29% for full papers only); 23% (17/71) / 33% (17+8/75 including short papers) in 2015; 22% (19/86) / 37% (19 long + 13 short / 86 including short papers) in 2016, 40% (14 long + 10 / 60) in 2017, 37% (18 long + 11 short / 79) in 2018, 32% (21 full + 7 short / 88) in 2019, 33% (19 full + 6 short / 76) in 2020, 42% (19+3/52) in 2023. 5 papers were invited to submit (30% of new material would be expected) for a special issue in Springer’s LNCS Transactions on Computational Collective Intelligence (TCCI) in 2012.

Extensions: 2 weeks in 2012, 10 days in 2013, 14 days in 2014, 14 days in 2015, 19 days in 2016, 2 weeks in 2017, 7+2 days in 2018, 8+6 days in 2019, 12 days in 2020, 32 days in 2023, 21 days in 2024, 7 days in 2025, 14 days (2026)

Kept verbatim from the old site while it is being turned into structured data.

Spotted something wrong on this page? Tell us, with a source if you have one ↗

Data entirely hand-typed, one call for papers at a time. There is no scraper behind any of this: I read the call for papers and/or the Web sites and type the dates in, in the gaps between other work, and with the hope it is useful to others. Organisers might then move deadlines without telling anyone, which may lead to inconsistencies. So, treat this small page as a well-meaning notebook rather than an authority 🤓