BIZTRAC BETA
Manufacture of metal structures and parts of structures

TIGMEK EIENDOM AS

Org. no. 821129702 Limited company (AS) Kristiansund Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK 1.9m
Equity NOK 6.7m
Incorporated 2018
Share capital NOK 30,000

Signals

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

TIGMEK EIENDOM AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 821129702. The business is classified under manufacture of metal structures and parts of structures (NACE 25.110). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie samt drifte næringseiendommer.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
Operating profit
NOK 1.9m
Equity
NOK 6.7m
Est. value
NOK 8.2m

Financial health · 2025

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

Who owns TIGMEK EIENDOM AS?

TIGMEK HOLDING AS
TIGMEK EIENDOM AS
NOK 2.7m rev. · NOK 1.9m profit

TIGMEK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TIGMEK EIENDOM AS

Who owns TIGMEK EIENDOM AS?

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

What is the revenue of TIGMEK EIENDOM AS?

TIGMEK EIENDOM AS had revenue of NOK 2.7m in 2025.

Who is the general manager of TIGMEK EIENDOM AS?

Bjørn Inge Neergaard is registered as general manager of TIGMEK EIENDOM AS.

Where is TIGMEK EIENDOM AS based?

TIGMEK EIENDOM AS has its business address in Frei.

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.