biztrac. BETA
COMPANY REGISTER PROFILE
923398082 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

REXEBASSEN AS

Org. no. 923398082 Limited company (AS) Bærum Incorporated 2019 Active
Revenue 2025 NOK 1.3m
Operating profit NOK 897,000
Equity NOK 22.9m
Incorporated 2019
Share capital NOK 1.4m

REXEBASSEN AS is registered as a limited company in Bærum, Akershus with organisation number 923398082. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2019. Registered share capital is NOK 1.4m, divided into 500 shares. The company's stated purpose is: “Å erverve, feste, bebygge, selge og bortleie fast eiendom og å gjøre seg interessert i andre foretagender med økonomisk formål, gjennom aksjekjøp eller på annen måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 897,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▲ +119 %
Operating profit
NOK 897,000
▲ +399 %
Equity
NOK 22.9m
▲ +4 %
Est. value
NOK 18.1m

Financial health · 2025

Liquidity
347.50
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 REXEBASSEN AS?

REXEBASSEN AS
NOK 1.3m rev. · NOK 897,000 profit

REXEBASSEN AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REXEBASSEN AS own?

REXEBASSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REXEBASSEN AS

Who owns REXEBASSEN AS?

Helene Grav is the largest registered owner, with 100.0%.

What is the revenue of REXEBASSEN AS?

REXEBASSEN AS had revenue of NOK 1.3m in 2025.

Where is REXEBASSEN AS based?

REXEBASSEN AS has its business address in Sandvika.

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.