BIZTRAC BETA
Repair and maintenance of civilian ships and boats

INMARTEK AS

Org. no. 997494237 Limited company (AS) Sør-Odal Incorporated 2011 Active
Ownership graph ↗
Revenue 2025 NOK 216,000
Operating profit NOK −10,000
Equity NOK 37,000
Incorporated 2011
Share capital NOK 150,000

Signals

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

INMARTEK AS is registered as a limited company in Sør-Odal, Innlandet with organisation number 997494237. The business is classified under repair and maintenance of civilian ships and boats (NACE 33.150). The company was incorporated in 2011. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Oppgradering, vedlikehold og oppussing av fritidsbåter i plast og tre, samt annen virksomhet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 216,000 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 216,000
Operating profit
NOK −10,000
Equity
NOK 37,000
Est. value
NOK 120,000

Financial health · 2025

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

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

Who owns INMARTEK AS?

MARIUS HAGBERG
INMARTEK AS
NOK 216,000 rev. · NOK −10,000 profit

INMARTEK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about INMARTEK AS

Who owns INMARTEK AS?

MARIUS HAGBERG is the largest registered owner, with 66.7%.

What is the revenue of INMARTEK AS?

INMARTEK AS had revenue of NOK 216,000 in 2025.

Who is the general manager of INMARTEK AS?

Marius Hagberg is registered as general manager of INMARTEK AS.

Where is INMARTEK AS based?

INMARTEK AS has its business address in Skarnes.

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.