BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

KROG AS

Org. no. 899229142 Limited company (AS) Gjøvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 1.3m
Equity NOK 5.7m
Incorporated 2012
Share capital NOK 138,000

KROG AS is registered as a limited company in Gjøvik, Innlandet with organisation number 899229142. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2012. Registered share capital is NOK 138,000, divided into 690 shares. The company's stated purpose is: “Kjøp, utleie og salg av fast eiendom, kjøp og salg av anleggsutstyr og maskiner. Produksjon, import og eksport av fjellboringsutstyr. Selskapet driver også med maskinhandel, handel med overskuddsmateriell og som maskinentreprenør, og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 1.3m
Equity
NOK 5.7m
Est. value
NOK 7.7m

Financial health · 2024

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

Who owns KROG AS?

TORKILD HANS KROG
KROG AS
NOK 1.8m rev. · NOK 1.3m profit

KROG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KROG AS

Who owns KROG AS?

TORKILD HANS KROG is the largest registered owner, with 100.0%.

What is the revenue of KROG AS?

KROG AS had revenue of NOK 1.8m in 2024.

Who is the general manager of KROG AS?

Torkild Hans Krog is registered as general manager of KROG AS.

Where is KROG AS based?

KROG AS has its business address in Hunndalen.

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.