BIZTRAC BETA
Plumbing installation

ERSTAD SERVICE AS

Org. no. 929030923 Limited company (AS) Sula Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 201,000
Operating profit NOK −17,000
Equity NOK 53,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−17k kr).

ERSTAD SERVICE AS is registered as a limited company in Sula, Møre og Romsdal with organisation number 929030923. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Service rørlegging, salg av deler og utstyr, utleie av servicepersonell og kjøp og salg av utstyr og verktøy, samt hva som er naturlig i den forbindelse. Herunder investeringer i andreselskap med tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 201,000 in revenue and NOK −17,000 in operating profit.

Key figures · 2025

Revenue
NOK 201,000
Operating profit
NOK −17,000
Equity
NOK 53,000
Est. value
NOK 93,000

Financial health · 2025

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

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

Who owns ERSTAD SERVICE AS?

MARTIN ERSTAD
ERSTAD SERVICE AS
NOK 201,000 rev. · NOK −17,000 profit

ERSTAD SERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ERSTAD SERVICE AS

Who owns ERSTAD SERVICE AS?

MARTIN ERSTAD is the largest registered owner, with 100.0%.

What is the revenue of ERSTAD SERVICE AS?

ERSTAD SERVICE AS had revenue of NOK 201,000 in 2025.

Where is ERSTAD SERVICE AS based?

ERSTAD SERVICE AS has its business address in Langevåg.

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.