BIZTRAC BETA
Wholesale of mining, construction and civil engineering machinery

NASTA AS

Org. no. 914523621 Limited company (AS) Larvik Incorporated 1976 Active
Ownership graph ↗
Revenue 2024 NOK 1.4bn
Operating profit NOK 36.2m
Equity NOK 229.9m
Incorporated 1976
Employees 220
Share capital NOK 1.5m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

NASTA AS is registered as a limited company in Larvik, Vestfold with organisation number 914523621. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 1976 and has 220 registered employees. Registered share capital is NOK 1.5m, divided into 5000 shares. The company's stated purpose is: “Handel og produksjon, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4bn in revenue and NOK 36.2m in operating profit.

Key figures · 2024

Revenue
NOK 1.4bn
Operating profit
NOK 36.2m
Equity
NOK 229.9m
Est. value
NOK 218.5m

Financial health · 2024

Liquidity
1.37
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
33.2%
Good
Equity as a share of total capital

Who owns NASTA AS?

SØRENCO AS
NASTA AS
NOK 1.4bn rev. · NOK 36.2m profit

NASTA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NASTA AS er morselskap for 5 datterselskaper:

Frequently asked questions about NASTA AS

Who owns NASTA AS?

SØRENCO AS is the largest registered owner, with 100.0%.

What is the revenue of NASTA AS?

NASTA AS had revenue of NOK 1.4bn in 2024.

Who is the general manager of NASTA AS?

Tom Johansen is registered as general manager of NASTA AS.

Where is NASTA AS based?

NASTA AS has its business address in Larvik.

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.