BIZTRAC BETA
Other printing

PRINTEX TRYKKERI AS

Org. no. 976535936 Limited company (AS) Hamar Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 6.4m
Operating profit NOK 375,000
Equity NOK 2.3m
Incorporated 1996
Share capital NOK 520,000

PRINTEX TRYKKERI AS is registered as a limited company in Hamar, Innlandet with organisation number 976535936. The business is classified under other printing (NACE 18.120). The company was incorporated in 1996. Registered share capital is NOK 520,000, divided into 520 shares. The company's stated purpose is: “Trykkerivirksomhet og handel i tilknytning til trykkerivirksomhet og hva dermed står i forbindelse. Selskapet kan videre eie og drive fast eiendom og kan likeledes ved aksjetegning eller på annen måte gjøre seg innteressert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.4m in revenue and NOK 375,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.4m
Operating profit
NOK 375,000
Equity
NOK 2.3m
Est. value
NOK 2.9m

Financial health · 2025

Liquidity
3.68
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
73.4%
Very good
Equity as a share of total capital

Who owns PRINTEX TRYKKERI AS?

ATLE FEJERSKOV JOHANSEN
PRINTEX TRYKKERI AS
NOK 6.4m rev. · NOK 375,000 profit

PRINTEX TRYKKERI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about PRINTEX TRYKKERI AS

Who owns PRINTEX TRYKKERI AS?

ATLE FEJERSKOV JOHANSEN is the largest registered owner, with 65.4%.

What is the revenue of PRINTEX TRYKKERI AS?

PRINTEX TRYKKERI AS had revenue of NOK 6.4m in 2025.

Who is the general manager of PRINTEX TRYKKERI AS?

Atle Fejerskov Johansen is registered as general manager of PRINTEX TRYKKERI AS.

Where is PRINTEX TRYKKERI AS based?

PRINTEX TRYKKERI AS has its business address in Hamar.

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.