BIZTRAC BETA
Repair and maintenance of machinery

EIDE SERVICE & VEDLIKEHOLD AS

Org. no. 832091952 Limited company (AS) Kvam Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 189,000
Operating profit NOK −16,000
Equity NOK 57,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−16k kr).

EIDE SERVICE & VEDLIKEHOLD AS is registered as a limited company in Kvam, Vestland with organisation number 832091952. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utleige av tjenester innen bygg og anlegg, industri, utleige av utstyr og personell.”. The most recent filed accounts, for the 2024 financial year, show NOK 189,000 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 189,000
Operating profit
NOK −16,000
Equity
NOK 57,000
Est. value
NOK 67,000

Financial health · 2024

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

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

Who owns EIDE SERVICE & VEDLIKEHOLD AS?

MARTIN EIDE
EIDE SERVICE & VEDLIKEHOLD AS
NOK 189,000 rev. · NOK −16,000 profit

EIDE SERVICE & VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIDE SERVICE & VEDLIKEHOLD AS

Who owns EIDE SERVICE & VEDLIKEHOLD AS?

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

What is the revenue of EIDE SERVICE & VEDLIKEHOLD AS?

EIDE SERVICE & VEDLIKEHOLD AS had revenue of NOK 189,000 in 2024.

Where is EIDE SERVICE & VEDLIKEHOLD AS based?

EIDE SERVICE & VEDLIKEHOLD AS has its business address in Norheimsund.

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.