BIZTRAC BETA
Construction of residential and non-residential buildings

TEAM OTTO AS

Org. no. 983086098 Limited company (AS) Lier Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 375,000
Equity NOK −1.1m
Incorporated 2001
Share capital NOK 1.7m

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,1 mill kr).

TEAM OTTO AS is registered as a limited company in Lier, Buskerud with organisation number 983086098. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2001. Registered share capital is NOK 1.7m, divided into 425 shares. The company's stated purpose is: “Konsulent- og tjenestevirksomhet innen byggfag, samt annen beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 375,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 375,000
Equity
NOK −1.1m
Est. value
NOK 1.4m

Financial health · 2024

Liquidity
12.19
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-298.9%
Weak
Equity as a share of total capital

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

Who owns TEAM OTTO AS?

OTTO RUNE FØYN ROBSAHM
TEAM OTTO AS
NOK 1.6m rev. · NOK 375,000 profit

TEAM OTTO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TEAM OTTO AS own?

TEAM OTTO AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TEAM OTTO AS

Who owns TEAM OTTO AS?

OTTO RUNE FØYN ROBSAHM is the largest registered owner, with 50.1%.

What is the revenue of TEAM OTTO AS?

TEAM OTTO AS had revenue of NOK 1.6m in 2024.

Where is TEAM OTTO AS based?

TEAM OTTO AS has its business address in Reistad.

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.