BIZTRAC BETA
Uoppgitt

NMT BYGG&EIENDOM AS

Org. no. 919994150 Limited company (AS) Harstad Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −598
Equity NOK 43,000
Incorporated 2017
Share capital NOK 100,000

Signals

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

NMT BYGG&EIENDOM AS is registered as a limited company in Harstad, Troms with organisation number 919994150. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og utleie av fast eiendom, medvirke i andre selskaper innen samme virksomhet, samt alt som hører naturlig til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −598 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −598
Equity
NOK 43,000
Est. value
NOK 50,000

Financial health · 2025

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

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

Who owns NMT BYGG&EIENDOM AS?

KJELL-HARALD NORDMARK
NMT BYGG&EIENDOM AS
NOK 0 rev. · NOK −598 profit

NMT BYGG&EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NMT BYGG&EIENDOM AS

Who owns NMT BYGG&EIENDOM AS?

KJELL-HARALD NORDMARK is the largest registered owner, with 100.0%.

What is the revenue of NMT BYGG&EIENDOM AS?

NMT BYGG&EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of NMT BYGG&EIENDOM AS?

Kjell-Harald Nordmark is registered as general manager of NMT BYGG&EIENDOM AS.

Where is NMT BYGG&EIENDOM AS based?

NMT BYGG&EIENDOM AS has its business address in Harstad.

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.