BIZTRAC BETA
Rental and operating of own or leased real estate

NYDALSMARKA I AS

Org. no. 921658850 Limited company (AS) Gjøvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 7.1m
Operating profit NOK 3.2m
Equity NOK 10.4m
Incorporated 2018
Share capital NOK 830,000

Signals

1 flags
  • Nylig endring 2026-05-13 Adresseendring registrert 2026-05-13.

NYDALSMARKA I AS is registered as a limited company in Gjøvik, Innlandet with organisation number 921658850. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 830,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og drift av eiendommer, forvaltning av eierinteresser i andre selskap ved aksjetegning eller tilsvarende.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.1m in revenue and NOK 3.2m in operating profit.

Key figures · 2025

Revenue
NOK 7.1m
Operating profit
NOK 3.2m
Equity
NOK 10.4m
Est. value
NOK 10.1m

Financial health · 2025

Liquidity
0.07
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.5%
Satisfactory
Equity as a share of total capital

Who owns NYDALSMARKA I AS?

OLRUDGÅRDEN HOLDING AS
NYDALSMARKA I AS
NOK 7.1m rev. · NOK 3.2m profit

NYDALSMARKA I AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NYDALSMARKA I AS

Who owns NYDALSMARKA I AS?

OLRUDGÅRDEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of NYDALSMARKA I AS?

NYDALSMARKA I AS had revenue of NOK 7.1m in 2025.

Who is the general manager of NYDALSMARKA I AS?

Martin Rolf Zettervall is registered as general manager of NYDALSMARKA I AS.

Where is NYDALSMARKA I AS based?

NYDALSMARKA I AS has its business address in Gjøvik.

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.