BIZTRAC BETA
Uoppgitt

ROBØ AS

Org. no. 922797994 Limited company (AS) Sortland Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 120,000
Operating profit NOK −694,000
Equity NOK 15.4m
Incorporated 2019
Share capital NOK 162,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−694k kr).

ROBØ AS is registered as a limited company in Sortland, Nordland with organisation number 922797994. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 162,000, divided into 81 shares. The company's stated purpose is: “Investere i aksjer og verdipapirer, eie, kjøpe, selge og drive utleie av fast eiendom og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 120,000 in revenue and NOK −694,000 in operating profit.

Key figures · 2025

Revenue
NOK 120,000
Operating profit
NOK −694,000
Equity
NOK 15.4m
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns ROBØ AS?

ROGER BØRGE BENUM
ROBØ AS
NOK 120,000 rev. · NOK −694,000 profit

ROBØ AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROBØ AS own?

ROBØ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ROBØ AS

Who owns ROBØ AS?

ROGER BØRGE BENUM is the largest registered owner, with 100.0%.

What is the revenue of ROBØ AS?

ROBØ AS had revenue of NOK 120,000 in 2025.

Who is the general manager of ROBØ AS?

Roger Børge Benum is registered as general manager of ROBØ AS.

Where is ROBØ AS based?

ROBØ AS has its business address in Sortland.

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.