BIZTRAC BETA
COMPANY REGISTER PROFILE
993729051 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Industrial product and fashion design activities

INTERTRYKK DA

Org. no. 993729051 General partnership with shared liability (DA) Bodø Incorporated 2009 Active
Ownership graph ↗
Equity NOK −1
Incorporated 2009

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1 kr).

INTERTRYKK DA is registered as a general partnership with shared liability in Bodø, Nordland with organisation number 993729051. The business is classified under industrial product and fashion design activities (NACE 74.110). The company was incorporated in 2009. The company's stated purpose is: “Import, design og salg av tekstiler og reklameprodukter.”.

Former names: PROMERCH DA, SOULREBEL DA

Key figures · 2025

Equity
NOK −1

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns INTERTRYKK DA?

No shareholders are registered for INTERTRYKK DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about INTERTRYKK DA

Who is the general manager of INTERTRYKK DA?

Kristian Mikalsen is registered as general manager of INTERTRYKK DA.

Where is INTERTRYKK DA based?

INTERTRYKK DA has its business address in Bodø.

Property

Business address Galnåsmyra 41B, 8022 Bodø
Cadastral unit 1804-41/784/0/0
Building Andre småhus med 3 boliger eller flere · 4 units

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.