BIZTRAC BETA
Retail sale of clothing

ANTREKKSPARTNER AS

Org. no. 933277712 Limited company (AS) Larvik Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK −450,000
Equity NOK −262,000
Incorporated 2024
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−262k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−450k kr).

ANTREKKSPARTNER AS is registered as a limited company in Larvik, Vestfold with organisation number 933277712. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2024. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Handel med klær og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK −450,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK −450,000
Equity
NOK −262,000

Financial health · 2024

Liquidity
0.91
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-39.1%
Weak
Equity as a share of total capital

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

Who owns ANTREKKSPARTNER AS?

TBG HOLDING AS
ANTREKKSPARTNER AS
NOK 2.0m rev. · NOK −450,000 profit

ANTREKKSPARTNER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ANTREKKSPARTNER AS

Who owns ANTREKKSPARTNER AS?

TBG HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of ANTREKKSPARTNER AS?

ANTREKKSPARTNER AS had revenue of NOK 2.0m in 2024.

Who is the general manager of ANTREKKSPARTNER AS?

Vidar Eriksen is registered as general manager of ANTREKKSPARTNER AS.

Where is ANTREKKSPARTNER AS based?

ANTREKKSPARTNER AS has its business address in Larvik.

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.