BIZTRAC BETA
Other building completion and finishing

EIKO MONTASJE SERVICE AS

Org. no. 934224124 Limited company (AS) Sandnes Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 380,000
Operating profit NOK 19,000
Equity NOK 70,000
Incorporated 2024
Share capital NOK 30,000

EIKO MONTASJE SERVICE AS is registered as a limited company in Sandnes, Rogaland with organisation number 934224124. The business is classified under other building completion and finishing (NACE 43.350). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Montasje service. Drift og vedlikehold. Import og salg av produkter.”. The most recent filed accounts, for the 2025 financial year, show NOK 380,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 380,000
Operating profit
NOK 19,000
Equity
NOK 70,000
Est. value
NOK 68,000

Financial health · 2025

Liquidity
1.55
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
20.7%
Weak
Equity as a share of total capital

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

Who owns EIKO MONTASJE SERVICE AS?

KASPARS OZOLINS
EIKO MONTASJE SERVICE AS
NOK 380,000 rev. · NOK 19,000 profit

EIKO MONTASJE SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about EIKO MONTASJE SERVICE AS

Who owns EIKO MONTASJE SERVICE AS?

KASPARS OZOLINS is the largest registered owner, with 50.0%.

What is the revenue of EIKO MONTASJE SERVICE AS?

EIKO MONTASJE SERVICE AS had revenue of NOK 380,000 in 2025.

Who is the general manager of EIKO MONTASJE SERVICE AS?

Kaspars Ozolins is registered as general manager of EIKO MONTASJE SERVICE AS.

Where is EIKO MONTASJE SERVICE AS based?

EIKO MONTASJE SERVICE AS has its business address in Hommersåk.

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.