BIZTRAC BETA
Rental and operating of own or leased real estate

BOLIGNÆRING AS

Org. no. 982049083 Limited company (AS) Stavanger Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK −2.9m
Equity NOK 2.7m
Incorporated 2000
Share capital NOK 275,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,9 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BOLIGNÆRING AS is registered as a limited company in Stavanger, Rogaland with organisation number 982049083. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2000. Registered share capital is NOK 275,000, divided into 1620 shares. The company's stated purpose is: “Eie og drifte selskapets eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK −2.9m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK −2.9m
Equity
NOK 2.7m
Est. value
NOK 2.1m

Financial health · 2024

Liquidity
1.33
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
15.9%
Satisfactory
Equity as a share of total capital

Who owns BOLIGNÆRING AS?

ASP EIENDOM AS
BOLIGNÆRING AS
NOK 1.9m rev. · NOK −2.9m profit

BOLIGNÆRING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BOLIGNÆRING AS er morselskap for 1 datterselskap:

Frequently asked questions about BOLIGNÆRING AS

Who owns BOLIGNÆRING AS?

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

What is the revenue of BOLIGNÆRING AS?

BOLIGNÆRING AS had revenue of NOK 1.9m in 2024.

Where is BOLIGNÆRING AS based?

BOLIGNÆRING AS has its business address in Stavanger.

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.