BIZTRAC BETA
COMPANY REGISTER PROFILE
920625312 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Retail sale of sports equipment

BOGBI AS

Org. no. 920625312 Limited company (AS) Inderøy Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −4,000
Equity NOK −1.6m
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,6 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−4k kr).

BOGBI AS is registered as a limited company in Inderøy, Trøndelag with organisation number 920625312. The business is classified under retail sale of sports equipment (NACE 47.631). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge Bogbi lastesykler i Norge og Europa.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −4,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −4,000
▲ +90 %
Equity
NOK −1.6m
▼ −0 %

Financial health · 2025

Liquidity
0.24
Not satisfactory
Current assets ÷ current liabilities
Profitability
-0.6%
Not satisfactory
Return on total assets
Solidity
-227.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BOGBI AS?

BOGBI AS
NOK 0 rev. · NOK −4,000 profit

BOGBI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOGBI AS

Who owns BOGBI AS?

BOGBI SAS is the largest registered owner, with 100.0%.

What is the revenue of BOGBI AS?

BOGBI AS had revenue of NOK 0 in 2025.

Who is the general manager of BOGBI AS?

Eduardo Jose Moreno Nuñez is registered as general manager of BOGBI AS.

Where is BOGBI AS based?

BOGBI AS has its business address in Inderøy.

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.