BIZTRAC BETA
Repair and maintenance of machinery

ESPEDAL MASKINSERVICE AS

Org. no. 912115852 Limited company (AS) Sandnes Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 549,000
Equity NOK 1.3m
Incorporated 2013
Share capital NOK 30,000

ESPEDAL MASKINSERVICE AS is registered as a limited company in Sandnes, Rogaland with organisation number 912115852. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selskapets virksomhet er reparasjon av maskiner og utstyr og annet som følger dette. Kjøp og salg av varer og tjenester og annet som følger dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 549,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 549,000
Equity
NOK 1.3m
Est. value
NOK 2.5m

Financial health · 2025

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

Who owns ESPEDAL MASKINSERVICE AS?

TROND ARILD ESPEDAL
ESPEDAL MASKINSERVICE AS
NOK 3.0m rev. · NOK 549,000 profit

ESPEDAL MASKINSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ESPEDAL MASKINSERVICE AS

Who owns ESPEDAL MASKINSERVICE AS?

TROND ARILD ESPEDAL is the largest registered owner, with 100.0%.

What is the revenue of ESPEDAL MASKINSERVICE AS?

ESPEDAL MASKINSERVICE AS had revenue of NOK 3.0m in 2025.

Who is the general manager of ESPEDAL MASKINSERVICE AS?

Trond Arild Espedal is registered as general manager of ESPEDAL MASKINSERVICE AS.

Where is ESPEDAL MASKINSERVICE AS based?

ESPEDAL MASKINSERVICE AS has its business address in Forsand.

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.