BIZTRAC BETA
Retail sale of clothing

OUTLET SERVICE AS

Org. no. 925135690 Limited company (AS) Drammen Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 164,000
Operating profit NOK 9,000
Equity NOK 124,000
Incorporated 2020
Share capital NOK 30,000

OUTLET SERVICE AS is registered as a limited company in Drammen, Buskerud with organisation number 925135690. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Oppkjøp av konkursbo og deretter omsette varelageret, hovedsakelig innen klær og hva herved står i forbindelse. Selskapet kan også investere i aksjer/andeler av andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 164,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2024

Revenue
NOK 164,000
Operating profit
NOK 9,000
Equity
NOK 124,000
Est. value
NOK 107,000

Financial health · 2024

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

Who owns OUTLET SERVICE AS?

KENNETH ARTHUR MARTINI HASSELBERG
OUTLET SERVICE AS
NOK 164,000 rev. · NOK 9,000 profit

OUTLET SERVICE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OUTLET SERVICE AS

Who owns OUTLET SERVICE AS?

KENNETH ARTHUR MARTINI HASSELBERG is the largest registered owner, with 50.0%.

What is the revenue of OUTLET SERVICE AS?

OUTLET SERVICE AS had revenue of NOK 164,000 in 2024.

Who is the general manager of OUTLET SERVICE AS?

Kenneth Arthur Martini Hasselberg is registered as general manager of OUTLET SERVICE AS.

Where is OUTLET SERVICE AS based?

OUTLET SERVICE AS has its business address in Krokstadelva.

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.