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

HOLTERGÅRDEN AS

Org. no. 997116348 Limited company (AS) Nannestad Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 920,000
Operating profit NOK 581,000
Equity NOK 4.1m
Incorporated 2011
Share capital NOK 750,000

HOLTERGÅRDEN AS is registered as a limited company in Nannestad, Akershus with organisation number 997116348. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 750,000, divided into 7500 shares. The company's stated purpose is: “Drive og leie ut fast eiendom, utlån av ledig kapital og deltagelse i selskaper med lignende formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 920,000 in revenue and NOK 581,000 in operating profit.

Key figures · 2025

Revenue
NOK 920,000
▼ −6 %
Operating profit
NOK 581,000
▼ −10 %
Equity
NOK 4.1m
▲ +11 %
Est. value
NOK 4.2m

Financial health · 2025

Liquidity
1.41
Satisfactory
Current assets ÷ current liabilities
Profitability
10.6%
Good
Return on total assets
Solidity
71.8%
Very good
Equity as a share of total capital

Who owns HOLTERGÅRDEN AS?

HOLTERGÅRDEN AS
NOK 920,000 rev. · NOK 581,000 profit

HOLTERGÅRDEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HOLTERGÅRDEN AS

Who owns HOLTERGÅRDEN AS?

Geir Einar Sjaastad is the largest registered owner, with 50.0%.

What is the revenue of HOLTERGÅRDEN AS?

HOLTERGÅRDEN AS had revenue of NOK 920,000 in 2025.

Who is the general manager of HOLTERGÅRDEN AS?

Geir Einar Sjaastad is registered as general manager of HOLTERGÅRDEN AS.

Where is HOLTERGÅRDEN AS based?

HOLTERGÅRDEN AS has its business address in Holter.

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.