BIZTRAC BETA
Rental and operating of own or leased real estate

NYE FLØISBONNVEIEN 2-4 AS

Org. no. 922031703 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 14.9m
Operating profit NOK 7.4m
Equity NOK 4.0m
Incorporated 2018
Share capital NOK 30,000

Signals

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

NYE FLØISBONNVEIEN 2-4 AS is registered as a limited company in Oslo, Oslo with organisation number 922031703. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 14.9m in revenue and NOK 7.4m in operating profit.

Key figures · 2024

Revenue
NOK 14.9m
Operating profit
NOK 7.4m
Equity
NOK 4.0m
Est. value
NOK 6.3m

Financial health · 2024

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

Who owns NYE FLØISBONNVEIEN 2-4 AS?

SOFIEMYR NÆRING AS
NYE FLØISBONNVEIEN 2-4 AS
NOK 14.9m rev. · NOK 7.4m profit

NYE FLØISBONNVEIEN 2-4 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYE FLØISBONNVEIEN 2-4 AS

Who owns NYE FLØISBONNVEIEN 2-4 AS?

SOFIEMYR NÆRING AS is the largest registered owner, with 100.0%.

What is the revenue of NYE FLØISBONNVEIEN 2-4 AS?

NYE FLØISBONNVEIEN 2-4 AS had revenue of NOK 14.9m in 2024.

Where is NYE FLØISBONNVEIEN 2-4 AS based?

NYE FLØISBONNVEIEN 2-4 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.