biztrac. BETA
COMPANY REGISTER PROFILE
913264924 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Operation of gravel and sand pits and mining of clay and kaolin

KREGNESMO DRIFT AS

Org. no. 913264924 Limited company (AS) Melhus Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 118,000
Operating profit NOK 114,000
Equity NOK 946,000
Incorporated 2014
Share capital NOK 30,000

KREGNESMO DRIFT AS is registered as a limited company in Melhus, Trøndelag with organisation number 913264924. The business is classified under operation of gravel and sand pits and mining of clay and kaolin (NACE 08.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Uttak, bearbeiding og salg av sand og steinprodukter.”. The most recent filed accounts, for the 2025 financial year, show NOK 118,000 in revenue and NOK 114,000 in operating profit.

Key figures · 2025

Revenue
NOK 118,000
Operating profit
NOK 114,000
▲ +1465 %
Equity
NOK 946,000
▲ +14 %
Est. value
NOK 753,000

Financial health · 2025

Liquidity
16.95
Very good
Current assets ÷ current liabilities
Profitability
14.1%
Good
Return on total assets
Solidity
94.1%
Very good
Equity as a share of total capital

Who owns KREGNESMO DRIFT AS?

KREGNESMO DRIFT AS
NOK 118,000 rev. · NOK 114,000 profit

KREGNESMO DRIFT AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KREGNESMO DRIFT AS

Who owns KREGNESMO DRIFT AS?

Jarle Bakk is the largest registered owner, with 50.0%.

What is the revenue of KREGNESMO DRIFT AS?

KREGNESMO DRIFT AS had revenue of NOK 118,000 in 2025.

Who is the general manager of KREGNESMO DRIFT AS?

Lars Bull Bakk is registered as general manager of KREGNESMO DRIFT AS.

Where is KREGNESMO DRIFT AS based?

KREGNESMO DRIFT AS has its business address in Kvål.

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.