BIZTRAC BETA
Business and other management consultancy activities

TEAM6 AS

Org. no. 926079018 Limited company (AS) Asker Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 369,000
Operating profit NOK 347,000
Equity NOK 323,000
Incorporated 2020
Share capital NOK 30,000

TEAM6 AS is registered as a limited company in Asker, Akershus with organisation number 926079018. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulentbistand innen finansielle og regnskapsmessig relaterte områder, å investere, direkte og indirekte, i andre selskaper og andre finansielle instrumenter, samt tilknyttede tjenester til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 369,000 in revenue and NOK 347,000 in operating profit.

Key figures · 2024

Revenue
NOK 369,000
Operating profit
NOK 347,000
Equity
NOK 323,000
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns TEAM6 AS?

ROBERT SCHRAMA
TEAM6 AS
NOK 369,000 rev. · NOK 347,000 profit

TEAM6 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does TEAM6 AS own?

TEAM6 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TEAM6 AS

Who owns TEAM6 AS?

ROBERT SCHRAMA is the largest registered owner, with 50.0%.

What is the revenue of TEAM6 AS?

TEAM6 AS had revenue of NOK 369,000 in 2024.

Who is the general manager of TEAM6 AS?

Robert Schrama is registered as general manager of TEAM6 AS.

Where is TEAM6 AS based?

TEAM6 AS has its business address in Borgen.

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.