biztrac. BETA
COMPANY REGISTER PROFILE
931163132 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Site preparation

EK-MASKIN AS

Org. no. 931163132 Limited company (AS) Askvoll Incorporated 2023 Active
Revenue 2025 NOK 1.3m
Operating profit NOK −320,000
Equity NOK 128,000
Incorporated 2023
Share capital NOK 200,000

Signals

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

EK-MASKIN AS is registered as a limited company in Askvoll, Vestland with organisation number 931163132. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Kjøreoppdrag med traktor og henger, grunnarbeid, utleie av egen arbeidskraft, salg av pukk/skotstein, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −320,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
▼ −13 %
Operating profit
NOK −320,000
▼ −262 %
Equity
NOK 128,000
▼ −73 %
Est. value
NOK 58,000

Financial health · 2025

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
-21.5%
Not satisfactory
Return on total assets
Solidity
7.9%
Weak
Equity as a share of total capital

Who owns EK-MASKIN AS?

EK-MASKIN AS
NOK 1.3m rev. · NOK −320,000 profit

EK-MASKIN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EK-MASKIN AS

Who owns EK-MASKIN AS?

Espen Kvamme is the largest registered owner, with 100.0%.

What is the revenue of EK-MASKIN AS?

EK-MASKIN AS had revenue of NOK 1.3m in 2025.

Who is the general manager of EK-MASKIN AS?

Espen Kvamme is registered as general manager of EK-MASKIN AS.

Where is EK-MASKIN AS based?

EK-MASKIN AS has its business address in Askvoll.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.