BIZTRAC BETA
Business and other management consultancy activities

BALLERUD HAGEMØBLER AS

Org. no. 914719178 Limited company (AS) Ringerike Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 276,000
Operating profit NOK −753,000
Equity NOK 6.5m
Incorporated 2014
Share capital NOK 2.0m

Signals

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

BALLERUD HAGEMØBLER AS is registered as a limited company in Ringerike, Buskerud with organisation number 914719178. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2014. Registered share capital is NOK 2.0m, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet i forbindelse med salg av hageartikler samt alt som står i forbindelse med dette, samt å investere i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 276,000 in revenue and NOK −753,000 in operating profit.

Key figures · 2025

Revenue
NOK 276,000
Operating profit
NOK −753,000
Equity
NOK 6.5m
Est. value
NOK 3.4m

Financial health · 2025

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

Who owns BALLERUD HAGEMØBLER AS?

BENTE RYSGAARD GRØNLUND
BALLERUD HAGEMØBLER AS
NOK 276,000 rev. · NOK −753,000 profit

BALLERUD HAGEMØBLER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BALLERUD HAGEMØBLER AS

Who owns BALLERUD HAGEMØBLER AS?

BENTE RYSGAARD GRØNLUND is the largest registered owner, with 100.0%.

What is the revenue of BALLERUD HAGEMØBLER AS?

BALLERUD HAGEMØBLER AS had revenue of NOK 276,000 in 2025.

Where is BALLERUD HAGEMØBLER AS based?

BALLERUD HAGEMØBLER AS has its business address in Tyristrand.

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.