BIZTRAC BETA
Retail sale of other food

ISBLÅ AS

Org. no. 916770219 Limited company (AS) Tønsberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.4m
Operating profit NOK 482,000
Equity NOK 1.4m
Incorporated 2016
Share capital NOK 500,000

Signals

1 flags
  • Nylig endring 2026-07-21 Adresseendring registrert 2026-07-21.

ISBLÅ AS is registered as a limited company in Tønsberg, Vestfold with organisation number 916770219. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2016. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Kjøp, salg og markedsføring av ernæringsrike matvarer og kosttilskudd og andre produkter og tjenester som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.4m in revenue and NOK 482,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.4m
Operating profit
NOK 482,000
Equity
NOK 1.4m
Est. value
NOK 2.4m

Financial health · 2024

Liquidity
3.81
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
73.8%
Very good
Equity as a share of total capital

Who owns ISBLÅ AS?

ARCTICSOURCE1 AS
ISBLÅ AS
NOK 3.4m rev. · NOK 482,000 profit

ISBLÅ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ISBLÅ AS

Who owns ISBLÅ AS?

ARCTICSOURCE1 AS is the largest registered owner, with 100.0%.

What is the revenue of ISBLÅ AS?

ISBLÅ AS had revenue of NOK 3.4m in 2024.

Who is the general manager of ISBLÅ AS?

Jan Håkon Håkonsen is registered as general manager of ISBLÅ AS.

Where is ISBLÅ AS based?

ISBLÅ AS has its business address in Tønsberg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.