BIZTRAC BETA
Site preparation

KVINA MASKIN HOLDING AS

Org. no. 927434512 Limited company (AS) Kvinesdal Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK 4.2m
Equity NOK 6.4m
Incorporated 2021
Share capital NOK 164,000

KVINA MASKIN HOLDING AS is registered as a limited company in Kvinesdal, Agder with organisation number 927434512. The business is classified under site preparation (NACE 43.120). The company was incorporated in 2021. Registered share capital is NOK 164,000, divided into 820 shares. The company's stated purpose is: “Investering i og deltakelse i andre selskaper, investering i verdipapirer, investering i og drift av eiendom, yte tjenester av administrativ karakter, samt alt som står i naturlig forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK 4.2m in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK 4.2m
Equity
NOK 6.4m
Est. value
NOK 15.2m

Financial health · 2024

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

Who owns KVINA MASKIN HOLDING AS?

G HOLM HOLDING AS
KVINA MASKIN HOLDING AS
NOK 4.4m rev. · NOK 4.2m profit

KVINA MASKIN HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does KVINA MASKIN HOLDING AS own?

KVINA MASKIN HOLDING AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about KVINA MASKIN HOLDING AS

Who owns KVINA MASKIN HOLDING AS?

G HOLM HOLDING AS is the largest registered owner, with 22.0%.

What is the revenue of KVINA MASKIN HOLDING AS?

KVINA MASKIN HOLDING AS had revenue of NOK 4.4m in 2024.

Where is KVINA MASKIN HOLDING AS based?

KVINA MASKIN HOLDING AS has its business address in Øyestranda.

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.