BIZTRAC BETA
Business and other management consultancy activities

KLOKKARGARDEN AS

Org. no. 899589572 Limited company (AS) Hareid Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 712,000
Operating profit NOK 639,000
Equity NOK 1.5m
Incorporated 2013
Share capital NOK 30,000

KLOKKARGARDEN AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 899589572. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Gardsbutikk med salg av egg, honning og andre gards relaterte varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 712,000 in revenue and NOK 639,000 in operating profit.

Key figures · 2025

Revenue
NOK 712,000
Operating profit
NOK 639,000
Equity
NOK 1.5m
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns KLOKKARGARDEN AS?

ELISABETH MYRENE
KLOKKARGARDEN AS
NOK 712,000 rev. · NOK 639,000 profit

KLOKKARGARDEN AS has 2 registered shareholders:

All shareholders and roles →

Which companies does KLOKKARGARDEN AS own?

KLOKKARGARDEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about KLOKKARGARDEN AS

Who owns KLOKKARGARDEN AS?

ELISABETH MYRENE is the largest registered owner, with 50.0%.

What is the revenue of KLOKKARGARDEN AS?

KLOKKARGARDEN AS had revenue of NOK 712,000 in 2025.

Who is the general manager of KLOKKARGARDEN AS?

Ingar Teigene is registered as general manager of KLOKKARGARDEN AS.

Where is KLOKKARGARDEN AS based?

KLOKKARGARDEN AS has its business address in Hareid.

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.