BIZTRAC BETA
Operation of gravel and sand pits and mining of clay and kaolin

LANGEBREKKE GRUSTAK AS

Org. no. 979792867 Limited company (AS) Indre Østfold Incorporated 1998 Active
Ownership graph ↗
Revenue 2025 NOK 8.4m
Operating profit NOK 1.8m
Equity NOK 4.9m
Incorporated 1998
Share capital NOK 100,000

LANGEBREKKE GRUSTAK AS is registered as a limited company in Indre Østfold, Østfold with organisation number 979792867. 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 1998. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Utvinning og salg av stein og grus, og hva som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.4m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 8.4m
Operating profit
NOK 1.8m
Equity
NOK 4.9m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns LANGEBREKKE GRUSTAK AS?

JOHAN ANTON LANGEBREKKE NILSEN
LANGEBREKKE GRUSTAK AS
NOK 8.4m rev. · NOK 1.8m profit

LANGEBREKKE GRUSTAK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LANGEBREKKE GRUSTAK AS

Who owns LANGEBREKKE GRUSTAK AS?

JOHAN ANTON LANGEBREKKE NILSEN is the largest registered owner, with 100.0%.

What is the revenue of LANGEBREKKE GRUSTAK AS?

LANGEBREKKE GRUSTAK AS had revenue of NOK 8.4m in 2025.

Who is the general manager of LANGEBREKKE GRUSTAK AS?

Johan Anton Langebrekke Nilsen is registered as general manager of LANGEBREKKE GRUSTAK AS.

Where is LANGEBREKKE GRUSTAK AS based?

LANGEBREKKE GRUSTAK AS has its business address in Mysen.

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.