You are: Developers · Institutions · Citizens
AION·ANALYTICS / India

Products / Open-source developer infrastructure

Technical reference / Lithuania and European venues

AION Lithuanian Market Calendar

STATUTORY DAYS / MIC SESSIONS / TARGET SETTLEMENT / MIT

European Market Session and Lithuanian Business Calendar, accessible to developers worldwide.

Three different calendar questions for developers: is this a Lithuanian working day, a scheduled venue session, or a TARGET settlement day?

Free MIT Python software accessible to developers worldwide. Coverage is defined Lithuanian and European calendar scope, not every country or exchange. No AION account, API key, hosted inference or broker integration.

01 / THREE-CALENDAR COMPARISON

Business day, trading day and settlement day are not synonyms.

Choose the question before choosing the calendar.

  1. Lithuanian business dayWeekends and the Article 123 statutory rules. Not an individual bank's operating schedule.
  2. Venue trading sessionMIC, local IANA timezone and actually verified closure coverage. Not live market availability.
  3. TARGET settlement dayEuro settlement closure rules. Not end-to-end SEPA delivery or a bank-specific cutoff.
The same date can produce different valid answers. Keep each result and its source independent.
Examples distinguish statutory, venue and settlement calendars.
2026 exampleLithuanian business dayNasdaq BalticTARGET settlement
3 April / Good FridayYesXVIL, XRIS and XTAL closedNo
16 FebruaryNo / Lithuanian statutory holidayXVIL closed; other venue calendars must be checkedYes under the published TARGET rule

On narrow screens, scroll within the table; all rows remain visible vertically.

Use these distinctions for payroll and contracts, fintech scheduling, payments planning, data-gap classification and market-data applications. They do not establish individual bank processing times or guarantee a payment will settle.

02 / STATUTORY RULES

Sixteen holiday entries under Article 123.

Fourteen provisions cover sixteen holiday entries, including two-day Easter and Christmas provisions.
Date or ruleStatutory holiday
1 JanuaryNew Year's Day
16 FebruaryRestoration of the State of Lithuania
11 MarchRestoration of Independence
Western Easter SundayEaster Sunday
Following MondayEaster Monday
1 MayInternational Labour Day
First Sunday of MayMother's Day
First Sunday of JuneFather's Day
24 JuneDay of Dew and St John
6 JulyStatehood and National Anthem Day
15 AugustAssumption Day
1 NovemberAll Saints' Day
2 NovemberAll Souls' Day
24 DecemberChristmas Eve
25 DecemberChristmas Day
26 DecemberSecond Day of Christmas

On narrow screens, scroll within the table; all rows remain visible vertically.

Western Easter determines Easter Sunday and Monday. Mother's Day is the first Sunday of May; Father's Day is the first Sunday of June. Christmas Eve is a statutory holiday. Lithuania has no automatic substitute Monday for a holiday falling on a weekend.

Užgavėnės is an observance, not a statutory non-working day. Do not turn a cultural observance into a payroll or business-day closure.

The package computes the published statutory rules; legislation can change. Do not interpret rule computation as a perpetual legal-compliance guarantee.

03 / MIC AND TIMEZONE CONTRACT

Nineteen session templates do not mean nineteen verified holiday calendars.

Ordinary continuous-session definitions from the maintained source. Verify actual venue/year closure coverage.
MIC / venueIANA local zoneContinuous-session template
XVIL / Nasdaq VilniusEurope/Vilnius10:00-15:55
XRIS / Nasdaq RigaEurope/Riga10:00-15:55
XTAL / Nasdaq TallinnEurope/Tallinn10:00-15:55
XSTO / Nasdaq StockholmEurope/Stockholm09:00-17:25
XCSE / Nasdaq CopenhagenEurope/Copenhagen09:00-16:55
XHEL / Nasdaq HelsinkiEurope/Helsinki10:00-18:25
XPAR / Euronext ParisEurope/Paris09:00-17:30
XAMS / Euronext AmsterdamEurope/Amsterdam09:00-17:30
XBRU / Euronext BrusselsEurope/Brussels09:00-17:30
XLIS / Euronext LisbonEurope/Lisbon08:00-16:30
XMIL / Euronext MilanEurope/Rome09:00-17:30
XDUB / Euronext DublinEurope/Dublin08:00-16:30
XETR / XetraEurope/Berlin09:00-17:30
XMAD / MadridEurope/Madrid09:00-17:30
XWBO / ViennaEurope/Vienna09:00-17:30
XWAR / WarsawEurope/Warsaw09:00-17:00
XPRA / PragueEurope/Prague09:00-16:20
XBUD / BudapestEurope/Budapest09:00-17:00
ASEX / AthensEurope/Athens10:15-17:20

On narrow screens, scroll within the table; all rows remain visible vertically.

Verified 2026 closure scope: XVIL, XRIS and XTAL

The corrected public Lithuanian dataset 2026.11.15.1 lists Riga (XRIS) closed on 18 November 2026, and all three Baltic venues closed all day on 31 December 2026. A missing closure entry for a different venue is not a live-open guarantee.

The 2026 review comprises 39 full-day closure records: Vilnius 13, Riga 14 and Tallinn 12. The manifest contains 2026 and 2027 files. File presence does not certify venue-specific 2027 completeness or extend the reviewed 2026 cohort to all nineteen MICs.

Local time, DST and UTC

Pass timezone-aware datetimes. A 10:00 session in Europe/Vilnius is 08:00 UTC in winter and 07:00 UTC in summer. Europe/Dublin has its own DST behavior; do not copy Vilnius's offset or treat a local clock as UTC.

For schedule-critical historical queries, use checked_session_bounds_utc to refuse unverified venue/year combinations; data_status() alone is not proof of complete venue coverage. The public phase contract models continuous trading or closed. It does not certify auctions, pre-open, post-close, unscheduled halts or broker execution permissions.

APPLIED / FIVE INTERNATIONAL EXAMPLES

Use it from anywhere. Ask only about the calendars it covers.

Worldwide accessibility means a developer in India or the United States can use the same library and aware timestamps. It does not add US, Indian or worldwide exchange calendars to this European package.

01 / An Indian developer checking Vilnius and Frankfurt from UTC

At 12:00 UTC on 13 November 2026, the same instant is 17:30 in Asia/Kolkata, 14:00 in Europe/Vilnius and 13:00 in Europe/Berlin. Pass that aware instant without manually shifting it. The Vilnius query can use reviewed 2026 closure data; Frankfurt's XETR entry is a session template, not equivalent verified holiday coverage. Check its official venue calendar before operational use.

Same instant, explicit zones / published 1.3.0
from datetime import datetime, timezone
from zoneinfo import ZoneInfo
from aion_lithuanian_market_calendar import is_open

at = datetime(2026, 11, 13, 12, tzinfo=timezone.utc)
assert at.astimezone(ZoneInfo("Asia/Kolkata")).hour == 17
assert at.astimezone(ZoneInfo("Europe/Vilnius")).hour == 14
assert at.astimezone(ZoneInfo("Europe/Berlin")).hour == 13
assert is_open(at, venue="XVIL") is True
# XETR has a template; validate its venue/year calendar separately.

02 / A US quant checking a past Baltic trading schedule

Use the original timestamp and MIC when aligning historical bars. For 13 November 2026, the verified Vilnius scheduled window is 08:00-13:55 UTC. Riga is closed on 18 November. These are scheduled-calendar answers, not evidence of historical fills, halts or tick delivery.

Verified closure versus an available scheduled window
from datetime import date
from aion_lithuanian_market_calendar import checked_session_bounds_utc

assert checked_session_bounds_utc(date(2026, 11, 18), "XRIS") is None
window = checked_session_bounds_utc(date(2026, 11, 13), "XVIL")
assert tuple(t.isoformat() for t in window) == (
    "2026-11-13T08:00:00+00:00", "2026-11-13T13:55:00+00:00",
)

03 / A Lithuanian payroll or HR application counting working days

next_business_day("2026-12-24") returns 28 December 2026 after Christmas Eve, Christmas and the weekend. Statutory rules include Western Easter and first-Sunday Mother's/Father's Days; no substitute Monday is added for weekend holidays. This is a calendar input to payroll and contract workflows, not a wage calculation, employment-law opinion or universal deadline rule.

04 / A European fintech planning TARGET settlement dates

On 3 April 2026, Good Friday is a Lithuanian business day but TARGET is closed. next_settlement_day("2026-04-03") returns 7 April after the weekend and Easter Monday. Conversely, 16 February is a Lithuanian statutory holiday while TARGET can settle. These rules support preliminary payment-date planning; they do not supply bank-specific cutoffs, SEPA delivery guarantees or an instrument's CSD settlement calendar.

05 / A data pipeline separating a closure from missing market data

A verified closed Riga date is different from an absent price bar during a scheduled Vilnius session. checked_session_bounds_utc returns a window or None only for a reviewed venue/year and generation, and raises for an unverified combination such as Xetra 2026. Keep three distinct states: scheduled closure, scheduled session with missing observations, and unknown coverage. Neither an empty feed nor a rule_only calendar proves an exchange closure.

Inspect data_status() and the original venue notice. Do not convert missing observations into a holiday, infer actual trading from a template, or use unsupported coverage as an open/closed decision.

04 / DATA LIFECYCLE

Compatible clients can adopt a corrected dataset independently.

Reviewed source to installed calendar data

  1. Primary source evidenceExchange, settlement or legal notice; a source observation is not an approved change.
  2. Publisher reviewReview date, jurisdiction and affected MIC/segment before publishing a versioned dataset.
  3. Public data channelApproved JSON files with manifest, version and SHA-256 bindings.
  4. Installed client checkCompatible client makes a bounded online check; offline policy can prevent it.
  5. Validate and adoptAccept a validated cache generation or retain the verified fallback; report its identity.
The public lt/ generation is 2026.11.15.1. Client adoption is conditional; it is not proof that every existing installation has received the correction.

Earlier 1.2.1 bundled outdated 2026 Baltic records. Published 1.3.0 bundles the corrected lt/ generation 2026.11.15.1, also available publicly at shared-source commit 91651c8c50852e7e82adb9986e6aa49129787cda. A compatible online client can adopt it without a new Python wheel, after manifest and every referenced payload verify. These are SHA-256 hash manifests, not digital signatures. Version 1.3.0 rejects older or conflicting data generations, including a forced refresh; that protection does not retroactively change 1.2.1 code.

Inspect data_status() for the actual loaded dataset/source. Offline or stale-cache installations may still use older data. No website statement substitutes for checking the installed generation and the original venue notice.

Earlier not-yet-published observations are superseded for these specific public releases. Publisher discovery, human approval and publication remain separate from the installed client's first-use, at-most-daily refresh. A complete unattended source-to-approval production pipeline is not established.

05 / SOFTWARE LIFECYCLE

Production automatic installation remains disabled in 1.3.0.

Separate Python package upgrade path

Normal supported path: the user controls the application interpreter.

  1. Published package releasePython code and bundled data in an approved PyPI distribution.
  2. Manual upgrade and verificationUser upgrades the application environment, checks its version and retests. This path ends here: no managed enrollment occurs.

Optional alternative / not production-activated

  1. Separate explicit enrollmentA user chooses a distinct owned managed runtime. Normal pip never makes this choice.
  2. Approved trust and policyIndependent signing, channel, bootstrap and compatibility admission are required.
  3. Isolated patch and rollbackHealth checks and workload controls precede any managed promotion. Production activation remains disabled.
The manual and experimental managed routes are separate choices. A new package release or data refresh silently activates neither a background service nor an application interpreter change.

Ordinary pip installs no scheduled service and does not silently switch existing applications to a managed interpreter. Earlier 1.2.1 contained neither the experimental managed controller nor user-visible upgrade notifications. Published 1.3.0 includes experimental components, but ordinary installation activates none of them.

The published 1.3.0 release passed its final package checks; those results do not approve production signing, channels, customer bootstrap or live workload enrollment. Windows updater rollout is paused. Windows 10 x64, native Windows 11 x64 and real reboot/logon acceptance remain unverified. Do not infer a consumer desktop guarantee from a Windows Server runner or ARM64 host running x64 Python.

A signed managed patch path would still require explicit enrollment, trusted policy, compatibility checks, workload admission and rollback. No promise covers automatic upgrades of every installed copy.

06 / PUBLISHED API EXAMPLES

Ask two independent questions of the same date.

Published package install
python -m pip install --upgrade aion-lithuanian-market-calendar
python -c "import importlib.metadata as m; print(m.version('aion-lithuanian-market-calendar'))"
Executed against published 1.3.0 code
from aion_lithuanian_market_calendar import (
    is_business_day, is_settlement_day,
)

# Good Friday: ordinary Lithuanian business day, TARGET closed.
assert is_business_day("2026-04-03") is True
assert is_settlement_day("2026-04-03") is False

# February16: statutory Lithuanian holiday, TARGET can settle.
assert is_business_day("2026-02-16") is False
assert is_settlement_day("2026-02-16") is True

For a venue query, provide its MIC and an aware instant to is_open or get_market_phase. For refreshed trading data, inspect data_status() and verify the actually adopted generation. These pure statutory/TARGET examples do not by themselves prove a refreshed venue dataset was loaded.

07 / SOURCES AND REVIEW BOUNDARIES

Keep legal rules, exchange evidence and data integrity separate.

Release identity: PyPI 1.3.0, with final CI evidence at source 30c11e3eae070546a123570d260513944039c526. Actual publication was 16 November 2026.

Wheel SHA-256: 1edb5563aa0b9b794083cbba4524899a9c54d32d462732d313e54537f97f12eb
Source distribution SHA-256: 3b7a4c5efcd84a6055c3e466fc39471358b8111ea6fdbbecefae60c07bc6d859

This is software documentation, not legal, tax or investment advice. No bank-specific cutoff, live exchange status, universal venue-calendar coverage or guaranteed payment result is supplied.

Support / reproducible calendar corrections

Show us the exact date and the expected answer.

For Lithuanian Market Calendar, email [email protected] or open a source issue. Include:

  • Package name and installed version
  • Dataset generation from the status helper
  • MIC or exchange/segment
  • Date, time and explicit timezone
  • Expected versus actual answer
  • Official source link and a minimal reproducer

Do not send credentials, customer records, account data, private strategies, orders or unnecessary personal information. This is a support contact, not a response-time guarantee.

Feedback on the Lithuanian Market Calendar

Something wrong, confusing or missing? Write it here. It goes straight to the team, and we read every message.

0 / 1971

We keep your message, your email if you give one, and a one-way code of your browser that only stops spam. Nothing is posted publicly.

Product-update emails: sign-up is temporarily unavailable while we repair the confirmation email. No address is being collected.