BIZTRAC BETA
Rental and operating of own or leased real estate

FRYSJAPARKEN FELT B NÆRING AS

Org. no. 925506508 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK 3.2m
Equity NOK 108.6m
Incorporated 2020
Share capital NOK 38,000

FRYSJAPARKEN FELT B NÆRING AS is registered as a limited company in Oslo, Oslo with organisation number 925506508. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 38,000, divided into 375 shares. The company's stated purpose is: “Investering i fast eiendom, herunder utleie, drift kjøp og salg, samt investering i aksjer og andre verdipapirer, herunder aktiv deltagelse i andre selskaper. I tillegg kommer annen nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK 3.2m in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK 3.2m
Equity
NOK 108.6m
Est. value
NOK 79.8m

Financial health · 2024

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

Who owns FRYSJAPARKEN FELT B NÆRING AS?

RAGDE EIENDOM AS
FRYSJAPARKEN FELT B NÆRING AS
NOK 5.7m rev. · NOK 3.2m profit

FRYSJAPARKEN FELT B NÆRING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRYSJAPARKEN FELT B NÆRING AS

Who owns FRYSJAPARKEN FELT B NÆRING AS?

RAGDE EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of FRYSJAPARKEN FELT B NÆRING AS?

FRYSJAPARKEN FELT B NÆRING AS had revenue of NOK 5.7m in 2024.

Where is FRYSJAPARKEN FELT B NÆRING AS based?

FRYSJAPARKEN FELT B NÆRING 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.