biztrac. BETA
COMPANY REGISTER PROFILE
922572364 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
In liquidation UPDATED 03.10.2026
⚠FRYSJA EIENDOM AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Civil engineering activities

FRYSJA EIENDOM AS

Org. no. 922572364 Limited company (AS) Oslo Incorporated 2019 In liquidation
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −185,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−185k kr).
  • Under avvikling Selskapet er under frivillig avvikling.

FRYSJA EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 922572364. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utvikling av eiendom”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −185,000
▼ −716 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

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

Who owns FRYSJA EIENDOM AS?

FRYSJA EIENDOM AS
NOK 0 rev. · NOK 0 profit

FRYSJA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRYSJA EIENDOM AS

Who owns FRYSJA EIENDOM AS?

Ole Karsten Ryen is the largest registered owner, with 50.0%.

What is the revenue of FRYSJA EIENDOM AS?

FRYSJA EIENDOM AS had revenue of NOK 0 in 2025.

Where is FRYSJA EIENDOM AS based?

FRYSJA EIENDOM 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.