BIZTRAC BETA
Wholesale of other food

BALLSTAD AS

Org. no. 921242816 Limited company (AS) Vestvågøy Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK −174,000
Equity NOK 6.7m
Incorporated 2018
Share capital NOK 43,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−174k kr).
  • Nylig endring 2026-05-04 Adresseendring registrert 2026-05-04.

BALLSTAD AS is registered as a limited company in Vestvågøy, Nordland with organisation number 921242816. The business is classified under wholesale of other food (NACE 46.380). The company was incorporated in 2018. Registered share capital is NOK 43,000, divided into 430391 shares. The company's stated purpose is: “Tjenester tilknyttet salg, import og eksport av fiskerelaterte produkter gjennom eget direkte salg via datterselskaper eller via agenter og distribusjonspartnere globalt.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK −174,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK −174,000
Equity
NOK 6.7m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns BALLSTAD AS?

LOFOTEN TRADING A/S
BALLSTAD AS
NOK 2.9m rev. · NOK −174,000 profit

BALLSTAD AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about BALLSTAD AS

Who owns BALLSTAD AS?

LOFOTEN TRADING A/S is the largest registered owner, with 36.1%.

What is the revenue of BALLSTAD AS?

BALLSTAD AS had revenue of NOK 2.9m in 2024.

Who is the general manager of BALLSTAD AS?

Trond Olav Olsen is registered as general manager of BALLSTAD AS.

Where is BALLSTAD AS based?

BALLSTAD AS has its business address in Leknes.

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.