BIZTRAC BETA
Wholesale of clothing and footwear

STIL OG TREND AS

Org. no. 998578612 Limited company (AS) Tønsberg Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 152,000
Operating profit NOK −62,000
Equity NOK 1.5m
Incorporated 2012
Share capital NOK 100,000

Signals

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

STIL OG TREND AS is registered as a limited company in Tønsberg, Vestfold with organisation number 998578612. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2012. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Import, eksport, salg av handelsvarer, rådgivning og salg av konsulent- og administrative tjenester, utleie av fast eiendom, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 152,000 in revenue and NOK −62,000 in operating profit.

Key figures · 2025

Revenue
NOK 152,000
Operating profit
NOK −62,000
Equity
NOK 1.5m
Est. value
NOK 747,000

Financial health · 2025

Liquidity
0.85
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
85.4%
Very good
Equity as a share of total capital

Who owns STIL OG TREND AS?

ROGER LØVENDAHL
STIL OG TREND AS
NOK 152,000 rev. · NOK −62,000 profit

STIL OG TREND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STIL OG TREND AS

Who owns STIL OG TREND AS?

ROGER LØVENDAHL is the largest registered owner, with 100.0%.

What is the revenue of STIL OG TREND AS?

STIL OG TREND AS had revenue of NOK 152,000 in 2025.

Who is the general manager of STIL OG TREND AS?

Roger Løvendahl is registered as general manager of STIL OG TREND AS.

Where is STIL OG TREND AS based?

STIL OG TREND AS has its business address in Vear.

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.