biztrac. BETA
COMPANY REGISTER PROFILE
997024559 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Manufacture of machinery for mining, quarrying and construction

KROG MASKIN AS

Org. no. 997024559 Limited company (AS) Gjøvik Incorporated 2011 Active
Revenue 2025 NOK 6.0m
Operating profit NOK 1.8m
Equity NOK 4.7m
Incorporated 2011
Share capital NOK 62,000

KROG MASKIN AS is registered as a limited company in Gjøvik, Innlandet with organisation number 997024559. The business is classified under manufacture of machinery for mining, quarrying and construction (NACE 28.920). The company was incorporated in 2011. Registered share capital is NOK 62,000, divided into 310 shares. The company's stated purpose is: “Produksjon, import og eksport av fjellboringsutstyr. Selskapet driver også med maskinhandel, handel med overskuddsmateriell og som maskinentreprenør.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.0m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 6.0m
▲ +74 %
Operating profit
NOK 1.8m
▲ +226 %
Equity
NOK 4.7m
▲ +71 %
Est. value
NOK 4.7m

Financial health · 2025

Liquidity
3.74
Very good
Current assets ÷ current liabilities
Profitability
29.4%
Very good
Return on total assets
Solidity
64.2%
Very good
Equity as a share of total capital

Who owns KROG MASKIN AS?

KROG MASKIN AS
NOK 6.0m rev. · NOK 1.8m profit

KROG MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KROG MASKIN AS

Who owns KROG MASKIN AS?

Torkild Hans Krog is the largest registered owner, with 100.0%.

What is the revenue of KROG MASKIN AS?

KROG MASKIN AS had revenue of NOK 6.0m in 2025.

Who is the general manager of KROG MASKIN AS?

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

Where is KROG MASKIN AS based?

KROG MASKIN 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.