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

GRENSESVINGEN 2-20 AS

Org. no. 923641270 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 61.6m
Operating profit NOK 25.6m
Equity NOK 445.6m
Incorporated 2019
Share capital NOK 2.0m

GRENSESVINGEN 2-20 AS is registered as a limited company in Bærum, Akershus with organisation number 923641270. 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 2.0m, divided into 1 shares. The company's stated purpose is: “Å investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 61.6m in revenue and NOK 25.6m in operating profit.

Former names: ARCTIC PROSJEKT 159 AS, HELSFYR KONTORHOLDING III B AS

Key figures · 2025

Revenue
NOK 61.6m
▲ +3 %
Operating profit
NOK 25.6m
▼ −85 %
Equity
NOK 445.6m
▼ −4 %
Est. value
NOK 379.8m

Financial health · 2025

Liquidity
5.04
Very good
Current assets ÷ current liabilities
Profitability
2.4%
Weak
Return on total assets
Solidity
38.6%
Good
Equity as a share of total capital

Who owns GRENSESVINGEN 2-20 AS?

GRENSESVINGEN 2-20 AS
NOK 61.6m rev. · NOK 25.6m profit

GRENSESVINGEN 2-20 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRENSESVINGEN 2-20 AS

Who owns GRENSESVINGEN 2-20 AS?

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

What is the revenue of GRENSESVINGEN 2-20 AS?

GRENSESVINGEN 2-20 AS had revenue of NOK 61.6m in 2025.

Where is GRENSESVINGEN 2-20 AS based?

GRENSESVINGEN 2-20 AS has its business address in Lysaker.

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.