BIZTRAC BETA
Other printing

EKH GRAFISK AS

Org. no. 956433460 Limited company (AS) Hustadvika Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 31.2m
Operating profit NOK 2.0m
Equity NOK 1.3m
Incorporated 1989
Employees 13
Share capital NOK 322,000

EKH GRAFISK AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 956433460. The business is classified under other printing (NACE 18.120). The company was incorporated in 1989 and has 13 registered employees. Registered share capital is NOK 322,000, divided into 322 shares. The company's stated purpose is: “Handel og trykkerivirksomhet samt alt som står i forbindelse med dette, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 31.2m in revenue and NOK 2.0m in operating profit.

Key figures · 2024

Revenue
NOK 31.2m
Operating profit
NOK 2.0m
Equity
NOK 1.3m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns EKH GRAFISK AS?

FRÆNA TRYKK AS
EKH GRAFISK AS
NOK 31.2m rev. · NOK 2.0m profit

EKH GRAFISK AS has 3 registered shareholders:

All shareholders and roles →

Which companies does EKH GRAFISK AS own?

EKH GRAFISK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about EKH GRAFISK AS

Who owns EKH GRAFISK AS?

FRÆNA TRYKK AS is the largest registered owner, with 50.0%.

What is the revenue of EKH GRAFISK AS?

EKH GRAFISK AS had revenue of NOK 31.2m in 2024.

Who is the general manager of EKH GRAFISK AS?

Kjetil Ingemar Moen is registered as general manager of EKH GRAFISK AS.

Where is EKH GRAFISK AS based?

EKH GRAFISK AS has its business address in Malmefjorden.

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.