BIZTRAC BETA
Joinery installation

DIN PORTMONTØR AS

Org. no. 925720003 Limited company (AS) Narvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.2m
Operating profit NOK −195,000
Equity NOK 1.0m
Incorporated 2020
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−195k kr).

DIN PORTMONTØR AS is registered as a limited company in Narvik, Nordland with organisation number 925720003. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2020. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive kjøp og salg av bygningsvarer, snekring, montering av porter, reparasjoner og ombygginger. Selskapet kan også delta i annen økonomisk virksomhet, samt hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.2m in revenue and NOK −195,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.2m
Operating profit
NOK −195,000
Equity
NOK 1.0m
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns DIN PORTMONTØR AS?

OSRE HOLDING AS
DIN PORTMONTØR AS
NOK 2.2m rev. · NOK −195,000 profit

DIN PORTMONTØR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIN PORTMONTØR AS

Who owns DIN PORTMONTØR AS?

OSRE HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of DIN PORTMONTØR AS?

DIN PORTMONTØR AS had revenue of NOK 2.2m in 2025.

Who is the general manager of DIN PORTMONTØR AS?

Mina Kazjarov Schackt is registered as general manager of DIN PORTMONTØR AS.

Where is DIN PORTMONTØR AS based?

DIN PORTMONTØR AS has its business address in Narvik.

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.