BIZTRAC BETA
Retail sale of clothing

NEOZ TØNSBERG AS

Org. no. 923401342 Limited company (AS) Tønsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.3m
Operating profit NOK −250,000
Equity NOK 459,000
Incorporated 2019
Employees 8
Share capital NOK 400,000

Signals

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

NEOZ TØNSBERG AS is registered as a limited company in Tønsberg, Vestfold with organisation number 923401342. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2019 and has 8 registered employees. Registered share capital is NOK 400,000, divided into 4000 shares. The company's stated purpose is: “Butikkhandel med klær. Detaljhandel med moteklær og hva herved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.3m in revenue and NOK −250,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.3m
Operating profit
NOK −250,000
Equity
NOK 459,000
Est. value
NOK 2.0m

Financial health · 2024

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

Who owns NEOZ TØNSBERG AS?

JASMINE SUSANNE LAURITZEN
NEOZ TØNSBERG AS
NOK 7.3m rev. · NOK −250,000 profit

NEOZ TØNSBERG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NEOZ TØNSBERG AS

Who owns NEOZ TØNSBERG AS?

JASMINE SUSANNE LAURITZEN is the largest registered owner, with 85.0%.

What is the revenue of NEOZ TØNSBERG AS?

NEOZ TØNSBERG AS had revenue of NOK 7.3m in 2024.

Who is the general manager of NEOZ TØNSBERG AS?

Jasmine Susanne Lauritzen is registered as general manager of NEOZ TØNSBERG AS.

Where is NEOZ TØNSBERG AS based?

NEOZ TØNSBERG 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.