BIZTRAC BETA
COMPANY REGISTER PROFILE
989189484 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

KOLIBRI AS

Org. no. 989189484 Limited company (AS) Frogn Incorporated 2005 Active
Ownership graph ↗
Equity NOK 2.1m
Incorporated 2005
Share capital NOK 2.0m

KOLIBRI AS is registered as a limited company in Frogn, Akershus with organisation number 989189484. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 2.0m, divided into 20000 shares. The company's stated purpose is: “Investeringsvirksomhet i selskap, eiendom, verdipapirer, forvaltning av rettigheter samt alt hva som hører inn under dette.”.

Key figures · 2025

Equity
NOK 2.1m
▲ +0 %
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns KOLIBRI AS?

KOLIBRI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOLIBRI AS own?

KOLIBRI AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KOLIBRI AS

Who owns KOLIBRI AS?

PER ERIK JACOBSEN is the largest registered owner, with 100.0%.

Where is KOLIBRI AS based?

KOLIBRI AS has its business address in Drøbak.

Property

Business address Vindfangerveien 4, 1443 Drøbak
Cadastral unit 3214-86/474/0/0
Building Andre småhus med 3 boliger eller flere · 3 units

3 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.