BIZTRAC BETA
Plumbing installation

HEIKA RØR OG RENOVERING AS

Org. no. 912294277 Limited company (AS) Karlsøy Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 5.0m
Operating profit NOK 763,000
Equity NOK 3.5m
Incorporated 2013
Share capital NOK 30,000

HEIKA RØR OG RENOVERING AS is registered as a limited company in Karlsøy, Troms with organisation number 912294277. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rørlegging arbeid og snekring, montering og reprasjonsarbeid, kjøp, salg av matrialer, og andre produkter/tjenester som naturlig hører sammen med dette. ”. The most recent filed accounts, for the 2025 financial year, show NOK 5.0m in revenue and NOK 763,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.0m
Operating profit
NOK 763,000
Equity
NOK 3.5m
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns HEIKA RØR OG RENOVERING AS?

MARTIN HALVAR HEIKA
HEIKA RØR OG RENOVERING AS
NOK 5.0m rev. · NOK 763,000 profit

HEIKA RØR OG RENOVERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEIKA RØR OG RENOVERING AS

Who owns HEIKA RØR OG RENOVERING AS?

MARTIN HALVAR HEIKA is the largest registered owner, with 100.0%.

What is the revenue of HEIKA RØR OG RENOVERING AS?

HEIKA RØR OG RENOVERING AS had revenue of NOK 5.0m in 2025.

Who is the general manager of HEIKA RØR OG RENOVERING AS?

Martin Halvar Heika is registered as general manager of HEIKA RØR OG RENOVERING AS.

Where is HEIKA RØR OG RENOVERING AS based?

HEIKA RØR OG RENOVERING AS has its business address in Hansnes.

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.