BIZTRAC BETA
Rental and operating of own or leased real estate

PIRELIUS AS

Org. no. 989007114 Limited company (AS) Oslo Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 3.6m
Operating profit NOK 3.4m
Equity NOK 38.8m
Incorporated 2005
Share capital NOK 287,000

PIRELIUS AS is registered as a limited company in Oslo, Oslo with organisation number 989007114. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 287,000, divided into 260550 shares. The company's stated purpose is: “Handel, investering i fast eiendom og verdipapirer samt annen virksomhet i tilknytning til dette, herunder deltagelse i andre selskaper med tilsvarende virksomhet gjennom egen kapital, lån eller ved avgivelse av garantier.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.6m in revenue and NOK 3.4m in operating profit.

Key figures · 2024

Revenue
NOK 3.6m
Operating profit
NOK 3.4m
Equity
NOK 38.8m
Est. value
NOK 35.4m

Financial health · 2024

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

Who owns PIRELIUS AS?

PER PHILIP BERG
PIRELIUS AS
NOK 3.6m rev. · NOK 3.4m profit

PIRELIUS AS has 4 registered shareholders:

All shareholders and roles →

Which companies does PIRELIUS AS own?

PIRELIUS AS holds stakes in 4 companies:

See the full ownership structure →

Group structure

PIRELIUS AS er morselskap for 1 datterselskap:

Frequently asked questions about PIRELIUS AS

Who owns PIRELIUS AS?

PER PHILIP BERG is the largest registered owner, with 30.0%.

What is the revenue of PIRELIUS AS?

PIRELIUS AS had revenue of NOK 3.6m in 2024.

Where is PIRELIUS AS based?

PIRELIUS 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.