BIZTRAC BETA
Buying and selling of own real estate

BOMER BOLIG AS

Org. no. 928955443 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 156,000
Operating profit NOK 57,000
Equity NOK −373,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

BOMER BOLIG AS is registered as a limited company in Oslo, Oslo with organisation number 928955443. The business is classified under buying and selling of own real estate (NACE 68.110). 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 156,000 in revenue and NOK 57,000 in operating profit.

Key figures · 2024

Revenue
NOK 156,000
Operating profit
NOK 57,000
Equity
NOK −373,000
Est. value
NOK 389,000

Financial health · 2024

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

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

Who owns BOMER BOLIG AS?

BOMER AS
BOMER BOLIG AS
NOK 156,000 rev. · NOK 57,000 profit

BOMER BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOMER BOLIG AS

Who owns BOMER BOLIG AS?

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

What is the revenue of BOMER BOLIG AS?

BOMER BOLIG AS had revenue of NOK 156,000 in 2024.

Where is BOMER BOLIG AS based?

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