BIZTRAC BETA
Retail sale of games and toys

RINGO BODØ AS

Org. no. 920296785 Limited company (AS) Bodø Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 19.9m
Operating profit NOK 895,000
Equity NOK 546,000
Incorporated 2017
Employees 13
Share capital NOK 500,000

RINGO BODØ AS is registered as a limited company in Bodø, Nordland with organisation number 920296785. The business is classified under retail sale of games and toys (NACE 47.640). The company was incorporated in 2017 and has 13 registered employees. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Butikkhandel med hovedsak leker samt diverse annet. Kan også eie og investere i eiendom og aksjer, samt deltakelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 19.9m in revenue and NOK 895,000 in operating profit.

Key figures · 2025

Revenue
NOK 19.9m
Operating profit
NOK 895,000
Equity
NOK 546,000
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
7.4%
Weak
Equity as a share of total capital

Who owns RINGO BODØ AS?

BENHAM AS
RINGO BODØ AS
NOK 19.9m rev. · NOK 895,000 profit

RINGO BODØ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RINGO BODØ AS own?

RINGO BODØ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RINGO BODØ AS

Who owns RINGO BODØ AS?

BENHAM AS is the largest registered owner, with 100.0%.

What is the revenue of RINGO BODØ AS?

RINGO BODØ AS had revenue of NOK 19.9m in 2025.

Who is the general manager of RINGO BODØ AS?

Kristin Henriette Gjertsen Mentzoni is registered as general manager of RINGO BODØ AS.

Where is RINGO BODØ AS based?

RINGO BODØ AS has its business address in Bodø.

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.