BIZTRAC BETA
Other printing

TRYKKMANN PROFIL AS

Org. no. 924329920 Limited company (AS) Hadsel Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 12.7m
Operating profit NOK 895,000
Equity NOK 2.3m
Incorporated 2019
Employees 11
Share capital NOK 200,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

TRYKKMANN PROFIL AS is registered as a limited company in Hadsel, Nordland with organisation number 924329920. The business is classified under other printing (NACE 18.120). The company was incorporated in 2019 and has 11 registered employees. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Å drive reklamebyrå, samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.7m in revenue and NOK 895,000 in operating profit.

Key figures · 2025

Revenue
NOK 12.7m
Operating profit
NOK 895,000
Equity
NOK 2.3m
Est. value
NOK 4.2m

Financial health · 2025

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

Who owns TRYKKMANN PROFIL AS?

TRYKKMANN EIENDOM AS
TRYKKMANN PROFIL AS
NOK 12.7m rev. · NOK 895,000 profit

TRYKKMANN PROFIL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYKKMANN PROFIL AS

Who owns TRYKKMANN PROFIL AS?

TRYKKMANN EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of TRYKKMANN PROFIL AS?

TRYKKMANN PROFIL AS had revenue of NOK 12.7m in 2025.

Who is the general manager of TRYKKMANN PROFIL AS?

Rolf Ivan Iversen is registered as general manager of TRYKKMANN PROFIL AS.

Where is TRYKKMANN PROFIL AS based?

TRYKKMANN PROFIL AS has its business address in Stokmarknes.

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.