BIZTRAC BETA
Rental and operating of own or leased real estate

ENGERUDGÅRDEN AS

Org. no. 976556054 Limited company (AS) Gran Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 293,000
Operating profit NOK 103,000
Equity NOK 753,000
Incorporated 1996
Share capital NOK 100,000

ENGERUDGÅRDEN AS is registered as a limited company in Gran, Innlandet with organisation number 976556054. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 200 shares. The company's stated purpose is: “Eie, drive og utvikle forretningseiendommer samt utøve virksomhet som har tilknytning til dette, herunder utleie, samt delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 293,000 in revenue and NOK 103,000 in operating profit.

Key figures · 2024

Revenue
NOK 293,000
Operating profit
NOK 103,000
Equity
NOK 753,000
Est. value
NOK 783,000

Financial health · 2024

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

Who owns ENGERUDGÅRDEN AS?

O M HELLUM SKOFORRETNING AS
ENGERUDGÅRDEN AS
NOK 293,000 rev. · NOK 103,000 profit

ENGERUDGÅRDEN AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ENGERUDGÅRDEN AS

Who owns ENGERUDGÅRDEN AS?

O M HELLUM SKOFORRETNING AS is the largest registered owner, with 25.0%.

What is the revenue of ENGERUDGÅRDEN AS?

ENGERUDGÅRDEN AS had revenue of NOK 293,000 in 2024.

Who is the general manager of ENGERUDGÅRDEN AS?

Torgrim Dynna is registered as general manager of ENGERUDGÅRDEN AS.

Where is ENGERUDGÅRDEN AS based?

ENGERUDGÅRDEN AS has its business address in Brandbu.

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.