BIZTRAC BETA
Site preparation

ESPELUND MASKIN AS

Org. no. 929431413 Limited company (AS) Grong Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 4.1m
Operating profit NOK −599,000
Equity NOK −107,000
Incorporated 2022
Share capital NOK 50,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−107k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−599k kr).

ESPELUND MASKIN AS is registered as a limited company in Grong, Trøndelag with organisation number 929431413. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Selskapets formål er entreprenørvirksomhet, såsom graving, brøyting, kantklipping og skogrydding. I tillegg kan selskapet drive med utleie av maskiner og mannskap.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.1m in revenue and NOK −599,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.1m
Operating profit
NOK −599,000
Equity
NOK −107,000

Financial health · 2024

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-6.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ESPELUND MASKIN AS?

IVAR BJØRNAR ESPELUND
ESPELUND MASKIN AS
NOK 4.1m rev. · NOK −599,000 profit

ESPELUND MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESPELUND MASKIN AS

Who owns ESPELUND MASKIN AS?

IVAR BJØRNAR ESPELUND is the largest registered owner, with 100.0%.

What is the revenue of ESPELUND MASKIN AS?

ESPELUND MASKIN AS had revenue of NOK 4.1m in 2024.

Where is ESPELUND MASKIN AS based?

ESPELUND MASKIN AS has its business address in Grong.

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.