BIZTRAC BETA
COMPANY REGISTER PROFILE
823005032 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

BLIKI AS

Org. no. 823005032 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 237,000
Incorporated 2019
Share capital NOK 33,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

BLIKI AS is registered as a limited company in Bærum, Akershus with organisation number 823005032. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 33,000, divided into 325 shares. The company's stated purpose is: “Investeringsvirksomhet”.

Key figures · 2025

Operating profit
NOK −13,000
▼ −3 %
Equity
NOK 237,000
▼ −57 %
Est. value
NOK 279,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
-2.5%
Not satisfactory
Return on total assets
Solidity
100.0%
Very good
Equity as a share of total capital

Who owns BLIKI AS?

BLIKI AS
· NOK −13,000 profit

BLIKI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLIKI AS own?

BLIKI AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BLIKI AS

Who owns BLIKI AS?

INGIBJØRG MEYER-MYKLESTAD is the largest registered owner, with 100.0%.

Where is BLIKI AS based?

BLIKI AS has its business address in Snarøya.

Property

Business address Skogenbuen 3, 1367 Snarøya
Cadastral unit 3201-44/402/0/0
Building Tomannsbolig, vertikal · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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