order_spread_limit · hk_etf · Hong Kong (XHKG)

Definition (docs/SCHEMA.md, “Rule names · Hong Kong equities (XHKG) (2026.11.02)”): order_spread_limit — value: {max_spreads, wider_pct, reference}; meaning: Passive-side CTS limit-order quotation boundary: max_spreads spread steps from reference, or, where wider_pct is set, the wider of that and the wider_pct alternative; empty-book and first-quotation fallbacks are specified in notes. Continuous trading only: auction orders are excluded (see opening_auction_limit_pct / closing_auction_limit_pct). Exactly these keys, each as below; checked at load, for market XHKG only. Not a daily price limit: limit_price() does not use it.

Scope hk_etf: Exchange-traded funds listed on the SEHK securities market, excluding leveraged and inverse products; Marina coverage from 2010-01-01.

Timeline

marketeffective_fromeffective_tovalueunitverificationpublished_atrecord
XHKG2005-07-042023-03-20
max_spreads24
referencesame_side_best_or_rule_fallback
wider_pctnull
single-source2005-06-29hk.order_spread_limit.hk_etf.2005-07-04
XHKG2023-03-20open
max_spreads24
referencesame_side_best_or_rule_fallback
wider_pct0.035
single-source2023-02-13hk.order_spread_limit.hk_etf.2023-03-20

Records and sources

hk.order_spread_limit.hk_etf.2005-07-04

market
XHKG
interval
[2005-07-04, 2023-03-20)
value
max_spreads24
referencesame_side_best_or_rule_fallback
wider_pctnull
verification
single-source
published_at
2005-06-29
recorded_at
2026-11-05
data file
hk/equity.yaml

Notes: CTS passive-price boundary for ordinary limit orders under Rules 503, 506A and 507A; the same passive boundary also applies to enhanced limit orders. It is not a symmetric band around nominal price and is not the aggressive-side matching limit. With both queues present, a limit buy must be no lower than (current best bid minus 24 spread steps) and no higher than current best ask; a limit sell must be no higher than (current best ask plus 24 spread steps) and no lower than current best bid. For a non-opening buy, use current bid when the buy queue exists; otherwise use the lowest of current ask, previous close and day low if the sell queue exists, or the lowest of last ask, previous close and day low if both queues are empty. For a non-opening sell, use current ask when the sell queue exists; otherwise use the highest of current bid, previous close and day high if the buy queue exists, or the highest of last bid, previous close and day high if both queues are empty. When both queues are empty and neither previous close nor the relevant day low/high is available, the respective Rule 506A(4)/507A(4) spread restriction does not bind. The first quotation of the day in CTS uses previous close: a first buy with no first ask has a lower boundary, and a first sell with no first bid has an upper boundary; Rule 504 permits Exchange waiver, including ex-dividend cases. Rules 506A/507A do not apply to POS or CAS auction orders (Rule 505); consult the separate auction rules. Enhanced limit orders have a separate aggressive boundary governed by the rules in force on the date, and special limit orders have different rules; those boundaries are not the 24-spread field. Count price steps using the security's applicable tick_size_table and date. Rule 101 defines a spread by the Second Schedule; no explicit cross-band counting algorithm was located, so multiplying all 24 steps by the starting tick is not established by the cited text. The true 24-spread start is 4 July 2005 (eight to twenty-four); continuity between official restatements is inferred, hence single-source. This interval has the spread-only passive boundary (wider_pct null: 24 spreads only). Later percentage extensions are not backdated. ETF spreads use the ETF's own applicable Part A, B or D, not automatically the stock table. The Part B ETF exception is only a tick-table selection and does not create an order-rule scope.

hk.order_spread_limit.hk_etf.2023-03-20

market
XHKG
interval
[2023-03-20, open)
value
max_spreads24
referencesame_side_best_or_rule_fallback
wider_pct0.035
verification
single-source
published_at
2023-02-13
recorded_at
2026-11-05
data file
hk/equity.yaml

Notes: CTS passive-price boundary for ordinary limit orders under Rules 503, 506A and 507A; the same passive boundary also applies to enhanced limit orders. It is not a symmetric band around nominal price and is not the aggressive-side matching limit. With both queues present, a limit buy must be no lower than (current best bid minus 24 spread steps) and no higher than current best ask; a limit sell must be no higher than (current best ask plus 24 spread steps) and no lower than current best bid. For a non-opening buy, use current bid when the buy queue exists; otherwise use the lowest of current ask, previous close and day low if the sell queue exists, or the lowest of last ask, previous close and day low if both queues are empty. For a non-opening sell, use current ask when the sell queue exists; otherwise use the highest of current bid, previous close and day high if the buy queue exists, or the highest of last bid, previous close and day high if both queues are empty. When both queues are empty and neither previous close nor the relevant day low/high is available, the respective Rule 506A(4)/507A(4) spread restriction does not bind. The first quotation of the day in CTS uses previous close: a first buy with no first ask has a lower boundary, and a first sell with no first bid has an upper boundary; Rule 504 permits Exchange waiver, including ex-dividend cases. Rules 506A/507A do not apply to POS or CAS auction orders (Rule 505); consult the separate auction rules. Enhanced limit orders have a separate aggressive boundary governed by the rules in force on the date, and special limit orders have different rules; those boundaries are not the 24-spread field. Count price steps using the security's applicable tick_size_table and date. Rule 101 defines a spread by the Second Schedule; no explicit cross-band counting algorithm was located, so multiplying all 24 steps by the starting tick is not established by the cited text. The true 24-spread start is 4 July 2005 (eight to twenty-four); continuity between official restatements is inferred, hence single-source. From 2023-03-20 the boundary is the wider of max_spreads (24 spreads) and wider_pct (3.5%) of the reference price; max_spreads alone is not an absolute cap of 24 price steps and cannot by itself reject an order. For a buy use min(reference minus 24 steps, reference times (1 minus 3.5%) rounded UP to a valid spread); for a sell use max(reference plus 24 steps, reference times (1 plus 3.5%) rounded DOWN to a valid spread). This substitutes for the passive boundary in each opening and missing-queue case above. There is no security-by-security phase-in. The 2 November 2026 pre-trade reform changes the separate multiplicative check (order_price_multiple_limit), not max_spreads or wider_pct. ETF spreads use the ETF's own applicable Part A, B or D, not automatically the stock table. The Part B ETF exception is only a tick-table selection and does not create an order-rule scope.

Known gaps

None recorded for this scope and rule.

Tracking

markettracked_through
XHKG2026-11-03

For a date on or before tracked_through, an open-ended record (effective_to: null) states what the sources said on that date. For a later date it is a carry-forward of the last checked rule, not a finding. A closed record is unaffected: its effective_to is itself sourced. A market or scope with no entry is untracked — no date is defaulted, and every open-ended answer on it is a carry-forward. (docs/SCHEMA.md, “Tracking registry”)

Ask it yourself

pip install marina-rules

import marina_rules as mr
mr.rule_at("order_spread_limit", "2023-03-20", "hk_etf", "XHKG")

marina-rules query order_spread_limit 2023-03-20 hk_etf XHKG

Cite

rules: marina-rules@2026.11.16 sha256:80188ec249ce22ae

Generated from the data of marina-rules 2026.11.16. Same facts as text: order_spread_limit.md. Treat the exchange's own notice as authoritative.

marina-rules — point-in-time trading rules as data. Install from PyPI · source, data and how to cite · CC0 data, MIT code.