BIZTRAC BETA
Rental and operating of own or leased real estate

BIVROST CAPITAL AS

Org. no. 919025387 Limited company (AS) Steinkjer Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 85,000
Operating profit NOK 24,000
Equity NOK 804,000
Incorporated 2017
Share capital NOK 600,000

Signals

1 flags
  • Nylig endring 2026-07-18 Avregistrert registrert 2026-07-18.

BIVROST CAPITAL AS is registered as a limited company in Steinkjer, Trøndelag with organisation number 919025387. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 600,000, divided into 2000 shares. The company's stated purpose is: “Konsulentvirksomhet, samt eie fast eiendom og investere i andre selskaper i inn og utland.”. The most recent filed accounts, for the 2024 financial year, show NOK 85,000 in revenue and NOK 24,000 in operating profit.

Key figures · 2024

Revenue
NOK 85,000
Operating profit
NOK 24,000
Equity
NOK 804,000
Est. value
NOK 597,000

Financial health · 2025

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

Who owns BIVROST CAPITAL AS?

ROCKLOVE AS
BIVROST CAPITAL AS
NOK 85,000 rev. · NOK 24,000 profit

BIVROST CAPITAL AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BIVROST CAPITAL AS own?

BIVROST CAPITAL AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BIVROST CAPITAL AS

Who owns BIVROST CAPITAL AS?

ROCKLOVE AS is the largest registered owner, with 50.0%.

What is the revenue of BIVROST CAPITAL AS?

BIVROST CAPITAL AS had revenue of NOK 85,000 in 2024.

Where is BIVROST CAPITAL AS based?

BIVROST CAPITAL AS has its business address in Steinkjer.

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.