BIZTRAC BETA
Rental and operating of own or leased real estate

AXEL SCHØYEN AS

Org. no. 944386025 Limited company (AS) Bærum Incorporated 1987 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK 1.6m
Equity NOK 75.8m
Incorporated 1987
Share capital NOK 104,000

AXEL SCHØYEN AS is registered as a limited company in Bærum, Akershus with organisation number 944386025. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1987. Registered share capital is NOK 104,000, divided into 324 shares. The company's stated purpose is: “Handelsvirksomhet og utleie -kjøp/salg av fast eiendom samt deltakelse i andre selskap ved aksje- tegning eller på annen måte.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK 1.6m in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK 1.6m
Equity
NOK 75.8m
Est. value
NOK 56.7m

Financial health · 2024

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

Who owns AXEL SCHØYEN AS?

KNUT EGIL BORGEN
AXEL SCHØYEN AS
NOK 2.9m rev. · NOK 1.6m profit

AXEL SCHØYEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does AXEL SCHØYEN AS own?

AXEL SCHØYEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about AXEL SCHØYEN AS

Who owns AXEL SCHØYEN AS?

KNUT EGIL BORGEN is the largest registered owner, with 89.8%.

What is the revenue of AXEL SCHØYEN AS?

AXEL SCHØYEN AS had revenue of NOK 2.9m in 2024.

Who is the general manager of AXEL SCHØYEN AS?

Knut Egil Borgen is registered as general manager of AXEL SCHØYEN AS.

Where is AXEL SCHØYEN AS based?

AXEL SCHØYEN AS has its business address in Jar.

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.