BIZTRAC BETA
Public relations and communication activities

TEAM LEADER AS

Org. no. 927282437 Limited company (AS) Tønsberg Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −4,000
Equity NOK 28,000
Incorporated 2021
Share capital NOK 46,000

Signals

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

TEAM LEADER AS is registered as a limited company in Tønsberg, Vestfold with organisation number 927282437. The business is classified under public relations and communication activities (NACE 73.300). The company was incorporated in 2021. Registered share capital is NOK 46,000, divided into 46140 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −4,000
Equity
NOK 28,000
Est. value
NOK 46,000

Financial health · 2025

Liquidity
0.15
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
63.9%
Weak
Equity as a share of total capital

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

Who owns TEAM LEADER AS?

ANDREAS HOLMBOE PARLOW
TEAM LEADER AS
· NOK −4,000 profit

TEAM LEADER AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TEAM LEADER AS own?

TEAM LEADER AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about TEAM LEADER AS

Who owns TEAM LEADER AS?

ANDREAS HOLMBOE PARLOW is the largest registered owner, with 100.0%.

Who is the general manager of TEAM LEADER AS?

Andreas Holmboe Parlow is registered as general manager of TEAM LEADER AS.

Where is TEAM LEADER AS based?

TEAM LEADER AS has its business address in Tønsberg.

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.