Norway · SWIFT/BIC
ASEANOK1XXX — ARCTIC SECURITIES AS
ASEANOK1XXX is the SWIFT/BIC code of ARCTIC SECURITIES AS, Oslo, Norway. You need it, together with the recipient's account number or IBAN, to send an international transfer to an account held there.
The first four characters, ASEA, identify the institution; NO is the ISO country code; K1 is the location code; XXX at the end means the head office, not a specific branch. It is the only ARCTIC SECURITIES AS code in the sources we use. The address shown is the registered address of the legal entity from its LEI record, not the counter where a branch operates.
Code details
| SWIFT/BIC code | ASEANOK1XXX |
|---|---|
| Institution | ARCTIC SECURITIES AS |
| Branch code | XXX (head office) |
| Country | Norway |
| City | Oslo |
| Postcode | 0161 |
| Registered address of the institution | Haakon VIIs gate 5, 0161, Oslo, 03, Norway |
| LEI | 5967007LIEEXZX4RVS72 |
| Entity status (GLEIF) | Active |
| Source | SWIFT/GLEIF BIC-to-LEI mapping + GLEIF LEI record, 2026-09-25 |
How to send money to ARCTIC SECURITIES AS
- Ask the recipient for their bank's SWIFT/BIC code and their account number or IBAN.
- Check that the code's characters 5–6 match the country of the recipient's bank.
- Use the 11-character code if the bank gave you one; an 8-character code addresses the head office.
- Open a PayerPay account, add the recipient with these details and send in their local currency.
Common questions
Which bank does ASEANOK1XXX belong to?
ARCTIC SECURITIES AS, Norway. It is the head-office code (branch code XXX).
Is ASEANOK1XXX an 8- or 11-character code?
ASEANOK1XXX is the 11-character form. The 8-character form, ASEANOK1, addresses the institution's head office; banks usually accept both for incoming transfers.
Can I send money with this code alone?
No. A SWIFT/BIC code identifies the bank; you also need the recipient's account number or IBAN, and in some countries a local routing code.
Where does this information come from?
The BIC-to-LEI mapping table published by SWIFT and GLEIF (version September 2026), GLEIF LEI reference data, and, where shown, the national bank register. Sources and dates are listed at the bottom of the page.
Where this data comes from
Codes on this page come from the BIC-to-LEI Mapping Table published by SWIFT and GLEIF (version September 2026, gleif.org). Institution names and registered addresses come from GLEIF Level‑1 LEI reference data (released under CC0, golden copy of 2026-09-29, terms). The entity status shown is the status of the legal entity in the Global LEI System, not a statement that a code is connected to SWIFT or valid for a particular payment.
SWIFT © and database rights September 2026. All rights reserved. This Mapping Table has been developed by SWIFT. Any use of the Mapping Table, in whole or in part, is subject to the BIC/LEI Mapping Table License Agreement as published with the Mapping Table available on GLEIF’s website. The Mapping Table is updated monthly. For the latest BIC information and updates, always refer to www.swift.com/bic.
PayerPay is not affiliated with, and this directory is not endorsed by, SWIFT, GLEIF or any of the central banks named above. Registers change; always confirm the code with the recipient's bank before sending a large transfer. Corrections: support@payerpay.io.
Who we are
PayerPay is operated by PAYER PAY INTERNATIONAL INC (Company ID BC1526086), registered with the Financial Transactions and Reports Analysis Centre of Canada under MSB registration C100001025 and with the Bank of Canada under the Retail Payment Activities Act. Payment details are issued through licensed banking partners.