BIZTRAC BETA
Retail sale of sports equipment

RIDER IN BALANCE AS

Org. no. 915545823 Limited company (AS) Grue Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.4m
Operating profit NOK −1.6m
Equity NOK 8.3m
Incorporated 2015
Share capital NOK 38,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,6 mill kr).

RIDER IN BALANCE AS is registered as a limited company in Grue, Innlandet with organisation number 915545823. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2015. Registered share capital is NOK 38,000, divided into 38064 shares. The company's stated purpose is: “Fremstilling/salg av rideteknisk utstyr og andre produkter som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.4m in revenue and NOK −1.6m in operating profit.

Key figures · 2024

Revenue
NOK 2.4m
Operating profit
NOK −1.6m
Equity
NOK 8.3m
Est. value
NOK 4.7m

Financial health · 2024

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

Who owns RIDER IN BALANCE AS?

MARIA TERESE KULBLIK ENGELL
RIDER IN BALANCE AS
NOK 2.4m rev. · NOK −1.6m profit

RIDER IN BALANCE AS has 19 registered shareholders:

All shareholders and roles →

Frequently asked questions about RIDER IN BALANCE AS

Who owns RIDER IN BALANCE AS?

MARIA TERESE KULBLIK ENGELL is the largest registered owner, with 46.7%.

What is the revenue of RIDER IN BALANCE AS?

RIDER IN BALANCE AS had revenue of NOK 2.4m in 2024.

Who is the general manager of RIDER IN BALANCE AS?

Maria Terese Kulblik Engell is registered as general manager of RIDER IN BALANCE AS.

Where is RIDER IN BALANCE AS based?

RIDER IN BALANCE AS has its business address in Grue Finnskog.

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.