BIZTRAC BETA
Rental and leasing of recreational and sports goods

BOBLEFOTBALL NORGE AS

Org. no. 915734499 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 1.1m
Operating profit NOK 110,000
Equity NOK 137,000
Incorporated 2015
Employees 7
Share capital NOK 30,000

BOBLEFOTBALL NORGE AS is registered as a limited company in Oslo, Oslo with organisation number 915734499. The business is classified under rental and leasing of recreational and sports goods (NACE 77.210). The company was incorporated in 2015 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive med salg og utleie av varer og tjenester, import og eksport av ulikt slag, og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.1m in revenue and NOK 110,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.1m
Operating profit
NOK 110,000
Equity
NOK 137,000
Est. value
NOK 545,000

Financial health · 2024

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

Who owns BOBLEFOTBALL NORGE AS?

HÅKON ØSTERBERG
BOBLEFOTBALL NORGE AS
NOK 1.1m rev. · NOK 110,000 profit

BOBLEFOTBALL NORGE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOBLEFOTBALL NORGE AS

Who owns BOBLEFOTBALL NORGE AS?

HÅKON ØSTERBERG is the largest registered owner, with 100.0%.

What is the revenue of BOBLEFOTBALL NORGE AS?

BOBLEFOTBALL NORGE AS had revenue of NOK 1.1m in 2024.

Who is the general manager of BOBLEFOTBALL NORGE AS?

Håkon Østerberg is registered as general manager of BOBLEFOTBALL NORGE AS.

Where is BOBLEFOTBALL NORGE AS based?

BOBLEFOTBALL NORGE AS has its business address in Oslo.

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.