BIZTRAC BETA
COMPANY REGISTER PROFILE
924033533 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

HEINY AS

Org. no. 924033533 Limited company (AS) Brønnøy Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK 894,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

HEINY AS is registered as a limited company in Brønnøy, Nordland with organisation number 924033533. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 550 shares. The company's stated purpose is: “Investering og deltakelse i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −16,000
▼ −8 %
Equity
NOK 894,000
▼ −12 %
Est. value
NOK 494,000

Financial health · 2025

Liquidity
4.94
Very good
Current assets ÷ current liabilities
Profitability
0.4%
Not satisfactory
Return on total assets
Solidity
83.6%
Very good
Equity as a share of total capital

Who owns HEINY AS?

HEINY AS
· NOK −16,000 profit

HEINY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEINY AS own?

HEINY AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HEINY AS

Who owns HEINY AS?

HEIDI TANGEN is the largest registered owner, with 100.0%.

Where is HEINY AS based?

HEINY AS has its business address in Brønnøysund.

Property

Business address Skrenten 5, 8909 Brønnøysund
Cadastral unit 1813-104/1160/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.