BIZTRAC BETA
Other building and industrial cleaning activities

SVANEN RENHOLD AS

Org. no. 821228352 Limited company (AS) Larvik Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 373,000
Operating profit NOK 41,000
Equity NOK 203,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-03 Adresseendring registrert 2026-06-03.

SVANEN RENHOLD AS is registered as a limited company in Larvik, Vestfold with organisation number 821228352. The business is classified under other building and industrial cleaning activities (NACE 81.220). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av renholdstjenester og alt som faller inn under dette, samt for øvrig deltal i annen næringsvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 373,000 in revenue and NOK 41,000 in operating profit.

Key figures · 2025

Revenue
NOK 373,000
Operating profit
NOK 41,000
Equity
NOK 203,000
Est. value
NOK 305,000

Financial health · 2025

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

Who owns SVANEN RENHOLD AS?

DAG TOMMY BREMSETH
SVANEN RENHOLD AS
NOK 373,000 rev. · NOK 41,000 profit

SVANEN RENHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SVANEN RENHOLD AS

Who owns SVANEN RENHOLD AS?

DAG TOMMY BREMSETH is the largest registered owner, with 100.0%.

What is the revenue of SVANEN RENHOLD AS?

SVANEN RENHOLD AS had revenue of NOK 373,000 in 2025.

Who is the general manager of SVANEN RENHOLD AS?

Dag Tommy Bremseth is registered as general manager of SVANEN RENHOLD AS.

Where is SVANEN RENHOLD AS based?

SVANEN RENHOLD 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.