BIZTRAC BETA
Growing of other non-perennial crops

STORE BALLER AS

Org. no. 928964523 Limited company (AS) Rendalen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 338,000
Operating profit NOK −61,000
Equity NOK 240,000
Incorporated 2022
Share capital NOK 480,000

Signals

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

STORE BALLER AS is registered as a limited company in Rendalen, Innlandet with organisation number 928964523. The business is classified under growing of other non-perennial crops (NACE 01.190). The company was incorporated in 2022. Registered share capital is NOK 480,000, divided into 480 shares. The company's stated purpose is: “Grovforproduksjon, utleie av maskiner og utstyr, utleie av arbeidskraft, leiekjøring, salg av varer, og andre produkter/tjenester som naturlig hører til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 338,000 in revenue and NOK −61,000 in operating profit.

Key figures · 2025

Revenue
NOK 338,000
Operating profit
NOK −61,000
Equity
NOK 240,000
Est. value
NOK 304,000

Financial health · 2025

Liquidity
0.73
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
25.1%
Good
Equity as a share of total capital

Who owns STORE BALLER AS?

AMUND BOLSTAD
STORE BALLER AS
NOK 338,000 rev. · NOK −61,000 profit

STORE BALLER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORE BALLER AS

Who owns STORE BALLER AS?

AMUND BOLSTAD is the largest registered owner, with 50.0%.

What is the revenue of STORE BALLER AS?

STORE BALLER AS had revenue of NOK 338,000 in 2025.

Who is the general manager of STORE BALLER AS?

Bjørn Halvor Trøen Granrud is registered as general manager of STORE BALLER AS.

Where is STORE BALLER AS based?

STORE BALLER AS has its business address in Rendalen.

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.