biztrac. BETA
COMPANY REGISTER PROFILE
811644412 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

REGALIS EIENDOM AS

Org. no. 811644412 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 22.3m
Operating profit NOK 446,000
Equity NOK 12.4m
Incorporated 2013
Share capital NOK 100,000

REGALIS EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 811644412. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2013. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Investering i og drift/utleie av fast eiendom. Selskapet kan også, som aksjeeier eller på annen måte, delta i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.3m in revenue and NOK 446,000 in operating profit.

Key figures · 2025

Revenue
NOK 22.3m
▲ +565 %
Operating profit
NOK 446,000
▲ +136 %
Equity
NOK 12.4m
▲ +356 %
Est. value
NOK 22.8m

Financial health · 2025

Liquidity
10.65
Very good
Current assets ÷ current liabilities
Profitability
28.9%
Very good
Return on total assets
Solidity
28.1%
Good
Equity as a share of total capital

Who owns REGALIS EIENDOM AS?

REGALIS EIENDOM AS
NOK 22.3m rev. · NOK 446,000 profit

REGALIS EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REGALIS EIENDOM AS

Who owns REGALIS EIENDOM AS?

Kjetil Brox is the largest registered owner, with 100.0%.

What is the revenue of REGALIS EIENDOM AS?

REGALIS EIENDOM AS had revenue of NOK 22.3m in 2025.

Who is the general manager of REGALIS EIENDOM AS?

Kjetil Brox is registered as general manager of REGALIS EIENDOM AS.

Where is REGALIS EIENDOM AS based?

REGALIS EIENDOM 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.