biztrac. BETA
COMPANY REGISTER PROFILE
992608234 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Landscape service activities

HJEM & HAGE AS

Org. no. 992608234 Limited company (AS) Klepp Incorporated 2008 Active
Revenue 2025 NOK 9.7m
Operating profit NOK 114,000
Equity NOK 411,000
Incorporated 2008
Employees 12
Share capital NOK 100,000

HJEM & HAGE AS is registered as a limited company in Klepp, Rogaland with organisation number 992608234. The business is classified under landscape service activities (NACE 81.300). The company was incorporated in 2008 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Malearbeid og tømmerarbeid, flislegging med mer, utvendig og innvendig arbeid. Opparbeiding og beplanting av hage og anlegg uteområder. Kjøp og salg av varer.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.7m in revenue and NOK 114,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.7m
▼ −2 %
Operating profit
NOK 114,000
▲ +141 %
Equity
NOK 411,000
▲ +39 %
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
6.4%
Satisfactory
Return on total assets
Solidity
21.2%
Good
Equity as a share of total capital

Who owns HJEM & HAGE AS?

HJEM & HAGE AS
NOK 9.7m rev. · NOK 114,000 profit

HJEM & HAGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HJEM & HAGE AS

Who owns HJEM & HAGE AS?

Miroslaw Korytkowski is the largest registered owner, with 100.0%.

What is the revenue of HJEM & HAGE AS?

HJEM & HAGE AS had revenue of NOK 9.7m in 2025.

Who is the general manager of HJEM & HAGE AS?

Miroslaw Korytkowski is registered as general manager of HJEM & HAGE AS.

Where is HJEM & HAGE AS based?

HJEM & HAGE AS has its business address in Kleppe.

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.