BIZTRAC BETA
Photographic activities

HEINSA AS

Org. no. 986336230 Limited company (AS) Trondheim Incorporated 2003 Active
Ownership graph ↗
Operating profit NOK −60,000
Equity NOK 2.8m
Incorporated 2003
Share capital NOK 3.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−60k kr).

HEINSA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 986336230. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2003. Registered share capital is NOK 3.0m, divided into 295000 shares. The company's stated purpose is: “Flyfotografering, land- industri- og sensormåling, kartproduksjon, systemutvikling, analog og digital visualisering, konsulent, prosjektengineering, eiendomsforvaltning og alt som hermed står i forbindelse. Ved etablering, aksjekjøp, lån, garantier eller på annen gjøre seg interessert i selskaper som virksomheter av lignende eller beslektet art, eller av annen art såfremt dette har betydning for selskapets andre aktiviteter. Formålet kan også fremmes ved deltagelse i eller i samarbeide med andre selskaper i inn- og utland.”.

Key figures · 2024

Operating profit
NOK −60,000
Equity
NOK 2.8m
Est. value
NOK 4.6m

Financial health · 2024

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

Who owns HEINSA AS?

REIDAR WIRUM BYE
HEINSA AS
· NOK −60,000 profit

HEINSA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about HEINSA AS

Who owns HEINSA AS?

REIDAR WIRUM BYE is the largest registered owner, with 98.0%.

Who is the general manager of HEINSA AS?

Reidar Wirum Bye is registered as general manager of HEINSA AS.

Where is HEINSA AS based?

HEINSA AS has its business address in Heimdal.

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.