BIZTRAC BETA
Research and experimental development on natural sciences and engineering

BOBLER AS

Org. no. 926900420 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 457,000
Operating profit NOK 75,000
Equity NOK −23,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−23k kr).

BOBLER AS is registered as a limited company in Oslo, Oslo with organisation number 926900420. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Naturvitenskapelig forskning og utvikling, konsulenttjenester samt design og produksjon av møbler”. The most recent filed accounts, for the 2025 financial year, show NOK 457,000 in revenue and NOK 75,000 in operating profit.

Key figures · 2025

Revenue
NOK 457,000
Operating profit
NOK 75,000
Equity
NOK −23,000
Est. value
NOK 686,000

Financial health · 2025

Liquidity
0.88
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-13.3%
Weak
Equity as a share of total capital

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

Who owns BOBLER AS?

PER CHRISTIAN SONTUM
BOBLER AS
NOK 457,000 rev. · NOK 75,000 profit

BOBLER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BOBLER AS

Who owns BOBLER AS?

PER CHRISTIAN SONTUM is the largest registered owner, with 100.0%.

What is the revenue of BOBLER AS?

BOBLER AS had revenue of NOK 457,000 in 2025.

Who is the general manager of BOBLER AS?

Per Christian Sontum is registered as general manager of BOBLER AS.

Where is BOBLER AS based?

BOBLER 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.