BIZTRAC BETA
Other technical consultancy

SERVICE MEKANIKEREN AS

Org. no. 929629108 Limited company (AS) Øygarden Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 165,000
Equity NOK 326,000
Incorporated 2022
Share capital NOK 30,000

SERVICE MEKANIKEREN AS is registered as a limited company in Øygarden, Vestland with organisation number 929629108. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge tjenester og varer innen anlegg og industri og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 165,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 165,000
Equity
NOK 326,000
Est. value
NOK 684,000

Financial health · 2024

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.7%
Good
Equity as a share of total capital

Who owns SERVICE MEKANIKEREN AS?

FRODE ELTVIK
SERVICE MEKANIKEREN AS
NOK 5.2m rev. · NOK 165,000 profit

SERVICE MEKANIKEREN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SERVICE MEKANIKEREN AS

Who owns SERVICE MEKANIKEREN AS?

FRODE ELTVIK is the largest registered owner, with 90.0%.

What is the revenue of SERVICE MEKANIKEREN AS?

SERVICE MEKANIKEREN AS had revenue of NOK 5.2m in 2024.

Who is the general manager of SERVICE MEKANIKEREN AS?

Frode Eltvik is registered as general manager of SERVICE MEKANIKEREN AS.

Where is SERVICE MEKANIKEREN AS based?

SERVICE MEKANIKEREN AS has its business address in Klokkarvik.

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.