BIZTRAC BETA
Rental and operating of own or leased real estate

PORTALEN BOLIGUTVIKLING AS

Org. no. 926289268 Limited company (AS) Øygarden Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK 168,000
Incorporated 2020
Share capital NOK 100,000

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-11 Adresseendring registrert 2026-04-11.

PORTALEN BOLIGUTVIKLING AS is registered as a limited company in Øygarden, Vestland with organisation number 926289268. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Erverv, utvikling, forvaltning og utleie av boligeiendom i sameie med boligkjøpere, samt deltagelse i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −21,000
Equity
NOK 168,000
Est. value
NOK 153,000

Financial health · 2024

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

Who owns PORTALEN BOLIGUTVIKLING AS?

SARTOR HOLDING AS
PORTALEN BOLIGUTVIKLING AS
· NOK −21,000 profit

PORTALEN BOLIGUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Group structure

PORTALEN BOLIGUTVIKLING AS er morselskap for 14 datterselskaper:

Frequently asked questions about PORTALEN BOLIGUTVIKLING AS

Who owns PORTALEN BOLIGUTVIKLING AS?

SARTOR HOLDING AS is the largest registered owner, with 100.0%.

Where is PORTALEN BOLIGUTVIKLING AS based?

PORTALEN BOLIGUTVIKLING AS has its business address in Straume.

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.