BIZTRAC BETA
Retail sale of clothing

SENIORKLÆR VESTFOLD AS

Org. no. 831902442 Limited company (AS) Tønsberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK −264,000
Equity NOK −198,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−198k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−264k kr).

SENIORKLÆR VESTFOLD AS is registered as a limited company in Tønsberg, Vestfold with organisation number 831902442. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Detaljsalg av seniorklær og andre produkter som hører sammen med dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK −264,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK −264,000
Equity
NOK −198,000

Financial health · 2025

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

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

Who owns SENIORKLÆR VESTFOLD AS?

RAVINDER SINGH
SENIORKLÆR VESTFOLD AS
NOK 1.2m rev. · NOK −264,000 profit

SENIORKLÆR VESTFOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SENIORKLÆR VESTFOLD AS

Who owns SENIORKLÆR VESTFOLD AS?

RAVINDER SINGH is the largest registered owner, with 100.0%.

What is the revenue of SENIORKLÆR VESTFOLD AS?

SENIORKLÆR VESTFOLD AS had revenue of NOK 1.2m in 2025.

Where is SENIORKLÆR VESTFOLD AS based?

SENIORKLÆR VESTFOLD AS has its business address in Sem.

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.