BIZTRAC BETA
COMPANY REGISTER PROFILE
981935098 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Non-specialised retail sale of predominately food, beverages or tobacco

ROBRU HANDELSLAG SA

Org. no. 981935098 Co-operation (SA) Gol Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 7.9m
Operating profit NOK −427,000
Equity NOK 2.3m
Incorporated 2000

Signals

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

ROBRU HANDELSLAG SA is registered as a co-operation in Gol, Buskerud with organisation number 981935098. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2000. The company's stated purpose is: “Drive handelsvirksomhet og hva dermed står i forbindelse og fremme medlemmenes forbruksmessige interesser, samt utleie av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.9m in revenue and NOK −427,000 in operating profit.

Former names: ROBRU HANDELSLAG BA

Key figures · 2025

Revenue
NOK 7.9m
Operating profit
NOK −427,000
Equity
NOK 2.3m
Est. value
NOK 3.3m

Financial health · 2025

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

Who owns ROBRU HANDELSLAG SA?

No shareholders are registered for ROBRU HANDELSLAG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ROBRU HANDELSLAG SA

What is the revenue of ROBRU HANDELSLAG SA?

ROBRU HANDELSLAG SA had revenue of NOK 7.9m in 2025.

Who is the general manager of ROBRU HANDELSLAG SA?

Iris Viljugrein is registered as general manager of ROBRU HANDELSLAG SA.

Where is ROBRU HANDELSLAG SA based?

ROBRU HANDELSLAG SA has its business address in Gol.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.