BIZTRAC BETA
Rental and operating of own or leased real estate

BIRKEDALSVEIEN 68 AS

Org. no. 922665281 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 61,000
Operating profit NOK −96,000
Equity NOK −1.1m
Incorporated 2019
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−96k kr).

BIRKEDALSVEIEN 68 AS is registered as a limited company in Kristiansand, Agder with organisation number 922665281. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Kjøpe, forvalte, leie ut og salg av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 61,000 in revenue and NOK −96,000 in operating profit.

Key figures · 2024

Revenue
NOK 61,000
Operating profit
NOK −96,000
Equity
NOK −1.1m

Financial health · 2024

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

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

Who owns BIRKEDALSVEIEN 68 AS?

JOHANNES RODRIGO MYHRE
BIRKEDALSVEIEN 68 AS
NOK 61,000 rev. · NOK −96,000 profit

BIRKEDALSVEIEN 68 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BIRKEDALSVEIEN 68 AS

Who owns BIRKEDALSVEIEN 68 AS?

JOHANNES RODRIGO MYHRE is the largest registered owner, with 100.0%.

What is the revenue of BIRKEDALSVEIEN 68 AS?

BIRKEDALSVEIEN 68 AS had revenue of NOK 61,000 in 2024.

Where is BIRKEDALSVEIEN 68 AS based?

BIRKEDALSVEIEN 68 AS has its business address in Søgne.

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.