biztrac. BETA
COMPANY REGISTER PROFILE
923836608 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

GRØDE EIENDOM AS

Org. no. 923836608 Limited company (AS) Hamar Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 866,000
Operating profit NOK 328,000
Equity NOK 677,000
Incorporated 2019
Share capital NOK 30,000

GRØDE EIENDOM AS is registered as a limited company in Hamar, Innlandet with organisation number 923836608. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utvikling av eiendom og hva dermed står i forbindelse, samt å interessere seg i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 866,000 in revenue and NOK 328,000 in operating profit.

Key figures · 2025

Revenue
NOK 866,000
▼ −17 %
Operating profit
NOK 328,000
▼ −39 %
Equity
NOK 677,000
▼ −2 %
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
6.6%
Satisfactory
Return on total assets
Solidity
14.0%
Satisfactory
Equity as a share of total capital

Who owns GRØDE EIENDOM AS?

GRØDE EIENDOM AS
NOK 866,000 rev. · NOK 328,000 profit

GRØDE EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GRØDE EIENDOM AS

Who owns GRØDE EIENDOM AS?

KAFFESELSKAPET AS is the largest registered owner, with 100.0%.

What is the revenue of GRØDE EIENDOM AS?

GRØDE EIENDOM AS had revenue of NOK 866,000 in 2025.

Who is the general manager of GRØDE EIENDOM AS?

Ole Gunnar Fagerås is registered as general manager of GRØDE EIENDOM AS.

Where is GRØDE EIENDOM AS based?

GRØDE EIENDOM AS has its business address in Hamar.

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.