BIZTRAC BETA
Rental and operating of own or leased real estate

BYFJORDPARKEN 15 AS

Org. no. 923561013 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 22.9m
Operating profit NOK 13.5m
Equity NOK 18.0m
Incorporated 2019
Share capital NOK 259,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BYFJORDPARKEN 15 AS is registered as a limited company in Oslo, Oslo with organisation number 923561013. 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 259,000, divided into 1 shares. The company's stated purpose is: “Eiendomsutvikling og forvaltning, investering i aksjer og andre eiendeler i andre selskaper, salg av konsulenttjenester, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 22.9m in revenue and NOK 13.5m in operating profit.

Key figures · 2024

Revenue
NOK 22.9m
Operating profit
NOK 13.5m
Equity
NOK 18.0m
Est. value
NOK 24.6m

Financial health · 2024

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

Who owns BYFJORDPARKEN 15 AS?

SAMARBEID I AS
BYFJORDPARKEN 15 AS
NOK 22.9m rev. · NOK 13.5m profit

BYFJORDPARKEN 15 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BYFJORDPARKEN 15 AS

Who owns BYFJORDPARKEN 15 AS?

SAMARBEID I AS is the largest registered owner, with 100.0%.

What is the revenue of BYFJORDPARKEN 15 AS?

BYFJORDPARKEN 15 AS had revenue of NOK 22.9m in 2024.

Where is BYFJORDPARKEN 15 AS based?

BYFJORDPARKEN 15 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.