BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

ULBO HANDEL AS

Org. no. 928830128 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 120.0m
Operating profit NOK 866,000
Equity NOK 3.1m
Incorporated 2022
Employees 37
Share capital NOK 500,000

ULBO HANDEL AS is registered as a limited company in Oslo, Oslo with organisation number 928830128. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2022 and has 37 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Selv, gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, å forestå drift av dagligvareforretning og annen virksomhet beslektet med denne.”. The most recent filed accounts, for the 2025 financial year, show NOK 120.0m in revenue and NOK 866,000 in operating profit.

Key figures · 2025

Revenue
NOK 120.0m
Operating profit
NOK 866,000
Equity
NOK 3.1m
Est. value
NOK 4.9m

Financial health · 2025

Liquidity
0.71
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.1%
Good
Equity as a share of total capital

Who owns ULBO HANDEL AS?

KAI-PETTER ULBO
ULBO HANDEL AS
NOK 120.0m rev. · NOK 866,000 profit

ULBO HANDEL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ULBO HANDEL AS

Who owns ULBO HANDEL AS?

KAI-PETTER ULBO is the largest registered owner, with 100.0%.

What is the revenue of ULBO HANDEL AS?

ULBO HANDEL AS had revenue of NOK 120.0m in 2025.

Who is the general manager of ULBO HANDEL AS?

Kai-Petter Ulbo is registered as general manager of ULBO HANDEL AS.

Where is ULBO HANDEL AS based?

ULBO HANDEL 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.