BIZTRAC BETA
Other printing

MODUM TEKSTILTRYKK AS

Org. no. 981937074 Limited company (AS) Modum Incorporated 2000 Active
Ownership graph ↗
Revenue 2024 NOK 33.3m
Operating profit NOK 5.6m
Equity NOK 19.8m
Incorporated 2000
Employees 11
Share capital NOK 100,000

MODUM TEKSTILTRYKK AS is registered as a limited company in Modum, Buskerud with organisation number 981937074. The business is classified under other printing (NACE 18.120). The company was incorporated in 2000 and has 11 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Trykkerivirksomhet, og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 33.3m in revenue and NOK 5.6m in operating profit.

Key figures · 2024

Revenue
NOK 33.3m
Operating profit
NOK 5.6m
Equity
NOK 19.8m
Est. value
NOK 29.8m

Financial health · 2024

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

Who owns MODUM TEKSTILTRYKK AS?

HARALD MIDTSKOGEN
MODUM TEKSTILTRYKK AS
NOK 33.3m rev. · NOK 5.6m profit

MODUM TEKSTILTRYKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does MODUM TEKSTILTRYKK AS own?

MODUM TEKSTILTRYKK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about MODUM TEKSTILTRYKK AS

Who owns MODUM TEKSTILTRYKK AS?

HARALD MIDTSKOGEN is the largest registered owner, with 100.0%.

What is the revenue of MODUM TEKSTILTRYKK AS?

MODUM TEKSTILTRYKK AS had revenue of NOK 33.3m in 2024.

Who is the general manager of MODUM TEKSTILTRYKK AS?

Harald Midtskogen is registered as general manager of MODUM TEKSTILTRYKK AS.

Where is MODUM TEKSTILTRYKK AS based?

MODUM TEKSTILTRYKK AS has its business address in Vikersund.

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.