BIZTRAC BETA
Rental and operating of own or leased real estate

SKÅRER BOLIGUTVIKLING AS

Org. no. 998901308 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 2.1m
Equity NOK 2.2m
Incorporated 2012
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.

SKÅRER BOLIGUTVIKLING AS is registered as a limited company in Oslo, Oslo with organisation number 998901308. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Eiendomsdrift og eiendomsutvikling samt investeringer, rådgivning og deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
Operating profit
NOK 2.1m
Equity
NOK 2.2m
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
48.4%
Very good
Equity as a share of total capital

Who owns SKÅRER BOLIGUTVIKLING AS?

OSLO EIENDOMSSENTER AS
SKÅRER BOLIGUTVIKLING AS
NOK 2.8m rev. · NOK 2.1m profit

SKÅRER BOLIGUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SKÅRER BOLIGUTVIKLING AS

Who owns SKÅRER BOLIGUTVIKLING AS?

OSLO EIENDOMSSENTER AS is the largest registered owner, with 100.0%.

What is the revenue of SKÅRER BOLIGUTVIKLING AS?

SKÅRER BOLIGUTVIKLING AS had revenue of NOK 2.8m in 2025.

Where is SKÅRER BOLIGUTVIKLING AS based?

SKÅRER BOLIGUTVIKLING 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.