BIZTRAC BETA
Manufacture of other special-purpose machinery n.e.c.

GUNDERSEN EIENDOM AS

Org. no. 974401622 Limited company (AS) Asker Incorporated 1995 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.1m
Equity NOK 7.1m
Incorporated 1995
Share capital NOK 100,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GUNDERSEN EIENDOM AS is registered as a limited company in Asker, Akershus with organisation number 974401622. The business is classified under manufacture of other special-purpose machinery n.e.c. (NACE 28.990). The company was incorporated in 1995. Registered share capital is NOK 100,000. The company's stated purpose is: “Investering i og utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.1m
Equity
NOK 7.1m
Est. value
NOK 8.0m

Financial health · 2025

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

Who owns GUNDERSEN EIENDOM AS?

S GUNDERSEN HOLDING AS
GUNDERSEN EIENDOM AS
NOK 1.8m rev. · NOK 1.1m profit

GUNDERSEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GUNDERSEN EIENDOM AS

Who owns GUNDERSEN EIENDOM AS?

S GUNDERSEN HOLDING AS is the largest registered owner, with 80.0%.

What is the revenue of GUNDERSEN EIENDOM AS?

GUNDERSEN EIENDOM AS had revenue of NOK 1.8m in 2025.

Who is the general manager of GUNDERSEN EIENDOM AS?

Svein Gundersen is registered as general manager of GUNDERSEN EIENDOM AS.

Where is GUNDERSEN EIENDOM AS based?

GUNDERSEN EIENDOM AS has its business address in Sætre.

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.