BIZTRAC BETA
Rental and operating of own or leased real estate

BOMER S2 AS

Org. no. 929270916 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −27,000
Equity NOK −28,000
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−28k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−27k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BOMER S2 AS is registered as a limited company in Oslo, Oslo with organisation number 929270916. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg, utvikling, drift og utleie av fast eiendom og aksjeinvesteringer samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −27,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −27,000
Equity
NOK −28,000

Financial health · 2024

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

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

Who owns BOMER S2 AS?

BOMER AS
BOMER S2 AS
NOK 0 rev. · NOK −27,000 profit

BOMER S2 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOMER S2 AS

Who owns BOMER S2 AS?

BOMER AS is the largest registered owner, with 100.0%.

What is the revenue of BOMER S2 AS?

BOMER S2 AS had revenue of NOK 0 in 2024.

Where is BOMER S2 AS based?

BOMER S2 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.