biztrac. BETA
COMPANY REGISTER PROFILE
819430152 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Plumbing installation

CSN RØRSERVICE AS

Org. no. 819430152 Limited company (AS) Tønsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 57,000
Equity NOK 564,000
Incorporated 2017
Share capital NOK 30,000

CSN RØRSERVICE AS is registered as a limited company in Tønsberg, Vestfold with organisation number 819430152. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “I hovedsak rørleggertjenester. I tillegg leveres alle typer håndverkstjenester og alt som hører til. Selskapet vil også investere i aksjer og andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 57,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
▼ −14 %
Operating profit
NOK 57,000
▼ −70 %
Equity
NOK 564,000
▲ +11 %
Est. value
NOK 583,000

Financial health · 2025

Liquidity
3.31
Very good
Current assets ÷ current liabilities
Profitability
11.0%
Good
Return on total assets
Solidity
81.4%
Very good
Equity as a share of total capital

Who owns CSN RØRSERVICE AS?

CSN RØRSERVICE AS
NOK 1.0m rev. · NOK 57,000 profit

CSN RØRSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CSN RØRSERVICE AS

Who owns CSN RØRSERVICE AS?

Cato Skjelbred Nilsen is the largest registered owner, with 100.0%.

What is the revenue of CSN RØRSERVICE AS?

CSN RØRSERVICE AS had revenue of NOK 1.0m in 2025.

Who is the general manager of CSN RØRSERVICE AS?

Cato Skjelbred Nilsen is registered as general manager of CSN RØRSERVICE AS.

Where is CSN RØRSERVICE AS based?

CSN RØRSERVICE 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.