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

IBLO AS

Org. no. 834412632 Limited company (AS) Bergen Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK 361,000
Incorporated 2024
Share capital NOK 450,000

Signals

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

IBLO AS is registered as a limited company in Bergen, Vestland with organisation number 834412632. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 450,000, divided into 900 shares. The company's stated purpose is: “Holdingselskap med eierskap i andre bedrifter.”.

Key figures · 2025

Operating profit
NOK −15,000
Equity
NOK 361,000
Est. value
NOK 425,000

Financial health · 2025

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

Who owns IBLO AS?

IBLO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does IBLO AS own?

IBLO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about IBLO AS

Who owns IBLO AS?

KNUT BØRSHEIM is the largest registered owner, with 51.0%.

Who is the general manager of IBLO AS?

Knut Børsheim is registered as general manager of IBLO AS.

Where is IBLO AS based?

IBLO AS has its business address in Søreidgrend.

Property

Business address Søvikhaugen 64, 5251 Søreidgrend
Cadastral unit 4601-38/151/0/0
Building Enebolig · 1 unit

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.