BIZTRAC BETA
Business and other management consultancy activities

FIVLINGEN INVEST AS

Org. no. 915487610 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −74,000
Equity NOK 6.0m
Incorporated 2015
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−74k kr).

FIVLINGEN INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 915487610. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Rådgivning, utleie av driftsmidler og deltakelse/investering i andre virksomheter og fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −74,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −74,000
Equity
NOK 6.0m
Est. value
NOK 8.6m

Financial health · 2024

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

Who owns FIVLINGEN INVEST AS?

LARS JOHAN SKEISVOLL HEREID
FIVLINGEN INVEST AS
NOK 0 rev. · NOK −74,000 profit

FIVLINGEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FIVLINGEN INVEST AS own?

FIVLINGEN INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about FIVLINGEN INVEST AS

Who owns FIVLINGEN INVEST AS?

LARS JOHAN SKEISVOLL HEREID is the largest registered owner, with 100.0%.

What is the revenue of FIVLINGEN INVEST AS?

FIVLINGEN INVEST AS had revenue of NOK 0 in 2024.

Where is FIVLINGEN INVEST AS based?

FIVLINGEN INVEST AS has its business address in Oslo.

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.