BIZTRAC BETA
Computer programming activities

TEAM VERTICAL AS

Org. no. 922390541 Limited company (AS) Nes Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK −27,000
Equity NOK 555,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−27k kr).

TEAM VERTICAL AS is registered as a limited company in Nes, Akershus with organisation number 922390541. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utvikling og salg av software, med salg av tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK −27,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK −27,000
Equity
NOK 555,000
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns TEAM VERTICAL AS?

VERTICAL EMPIRE AS
TEAM VERTICAL AS
NOK 1.7m rev. · NOK −27,000 profit

TEAM VERTICAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TEAM VERTICAL AS own?

TEAM VERTICAL AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TEAM VERTICAL AS

Who owns TEAM VERTICAL AS?

VERTICAL EMPIRE AS is the largest registered owner, with 100.0%.

What is the revenue of TEAM VERTICAL AS?

TEAM VERTICAL AS had revenue of NOK 1.7m in 2024.

Where is TEAM VERTICAL AS based?

TEAM VERTICAL AS has its business address in Hvam.

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.