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

BLÅSTÅL AS

Org. no. 928341658 Limited company (AS) Trondheim Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 914,000
Incorporated 2021
Share capital NOK 700,000

Signals

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

BLÅSTÅL AS is registered as a limited company in Trondheim, Trøndelag with organisation number 928341658. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 700,000, divided into 100 shares. The company's stated purpose is: “Eie og forvalte aksjer.”.

Key figures · 2025

Operating profit
NOK −3,000
▲ +0 %
Equity
NOK 914,000
▼ −0 %
Est. value
NOK 1.1m

Financial health · 2025

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

Who owns BLÅSTÅL AS?

BLÅSTÅL AS
· NOK −3,000 profit

BLÅSTÅL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BLÅSTÅL AS own?

BLÅSTÅL AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about BLÅSTÅL AS

Who owns BLÅSTÅL AS?

HANS KRISTIAN HEGLI is the largest registered owner, with 100.0%.

Where is BLÅSTÅL AS based?

BLÅSTÅL AS has its business address in Trondheim.

Property

Business address Marienbergveien 6A, 7020 Trondheim
Cadastral unit 5001-421/9/0/0
Building Tomannsbolig, horisontaldelt · 2 units

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.