BIZTRAC BETA
Joinery installation

EIMA SNEKKER AS

Org. no. 932353253 Limited company (AS) Hemnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 428,000
Operating profit NOK −222,000
Equity NOK −195,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−195k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−222k kr).

EIMA SNEKKER AS is registered as a limited company in Hemnes, Nordland with organisation number 932353253. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Snekkerarbeid, flislegging, malerarbeid og tapetsering.”. The most recent filed accounts, for the 2025 financial year, show NOK 428,000 in revenue and NOK −222,000 in operating profit.

Key figures · 2025

Revenue
NOK 428,000
Operating profit
NOK −222,000
Equity
NOK −195,000

Financial health · 2025

Liquidity
0.37
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-106.8%
Weak
Equity as a share of total capital

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

Who owns EIMA SNEKKER AS?

EIMONTAS KUPSYS
EIMA SNEKKER AS
NOK 428,000 rev. · NOK −222,000 profit

EIMA SNEKKER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EIMA SNEKKER AS

Who owns EIMA SNEKKER AS?

EIMONTAS KUPSYS is the largest registered owner, with 100.0%.

What is the revenue of EIMA SNEKKER AS?

EIMA SNEKKER AS had revenue of NOK 428,000 in 2025.

Who is the general manager of EIMA SNEKKER AS?

Eimontas Kupsys is registered as general manager of EIMA SNEKKER AS.

Where is EIMA SNEKKER AS based?

EIMA SNEKKER AS has its business address in Korgen.

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.