BIZTRAC BETA
Business and other management consultancy activities

VBI AS

Org. no. 995039753 Limited company (AS) Kristiansund Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 245,000
Operating profit NOK 95,000
Equity NOK −23,000
Incorporated 2010
Share capital NOK 150,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−23k kr).

VBI AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 995039753. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2010. Registered share capital is NOK 150,000, divided into 1500 shares. The company's stated purpose is: “Salg av tjenester og varer, konsulentvirksomhet, undervisningsvirksomhet og det som hører til dette, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 245,000 in revenue and NOK 95,000 in operating profit.

Key figures · 2024

Revenue
NOK 245,000
Operating profit
NOK 95,000
Equity
NOK −23,000
Est. value
NOK 431,000

Financial health · 2024

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-22.3%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VBI AS?

MAY-BRITT FLØNES
VBI AS
NOK 245,000 rev. · NOK 95,000 profit

VBI AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VBI AS own?

VBI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VBI AS

Who owns VBI AS?

MAY-BRITT FLØNES is the largest registered owner, with 50.0%.

What is the revenue of VBI AS?

VBI AS had revenue of NOK 245,000 in 2024.

Where is VBI AS based?

VBI AS has its business address in Kristiansund N.

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.