BIZTRAC BETA
Construction of residential and non-residential buildings

NYSTED AS

Org. no. 976074580 Limited company (AS) Balsfjord Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 135.5m
Operating profit NOK 6.2m
Equity NOK 52.1m
Incorporated 1995
Employees 70
Share capital NOK 800,000

NYSTED AS is registered as a limited company in Balsfjord, Troms with organisation number 976074580. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1995 and has 70 registered employees. Registered share capital is NOK 800,000. The company's stated purpose is: “Handel, entreprenørvirksomhet innen bygg og anlegg samt annen virksomhet som står i forbindelse, herunder å kunne delta som interessert i andre selskaper med virksomhet av forretningsmessig karakter.”. The most recent filed accounts, for the 2024 financial year, show NOK 135.5m in revenue and NOK 6.2m in operating profit.

Key figures · 2024

Revenue
NOK 135.5m
Operating profit
NOK 6.2m
Equity
NOK 52.1m
Est. value
NOK 45.5m

Financial health · 2024

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

Who owns NYSTED AS?

J NYSTED EIENDOM AS
NYSTED AS
NOK 135.5m rev. · NOK 6.2m profit

NYSTED AS has 1 registered shareholder:

All shareholders and roles →

Which companies does NYSTED AS own?

NYSTED AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

NYSTED AS er morselskap for 1 datterselskap:

Frequently asked questions about NYSTED AS

Who owns NYSTED AS?

J NYSTED EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of NYSTED AS?

NYSTED AS had revenue of NOK 135.5m in 2024.

Where is NYSTED AS based?

NYSTED AS has its business address in Storsteinnes.

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.