BIZTRAC BETA
Plumbing installation

KARL J SVENSEN AS

Org. no. 988536059 Limited company (AS) Sandefjord Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 6.1m
Operating profit NOK 234,000
Equity NOK 19.0m
Incorporated 2005
Employees 5
Share capital NOK 100,000

KARL J SVENSEN AS is registered as a limited company in Sandefjord, Vestfold with organisation number 988536059. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2005 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Rørleggervirksomhet herunder opplegg salg, produksjon og service av vann-, varme- og sanitæranlegg og alt hva hermed står i forbindelse, blant annet med deltakelse i andre selskaper eller virksomheter, samt investering i fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.1m in revenue and NOK 234,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.1m
Operating profit
NOK 234,000
Equity
NOK 19.0m
Est. value
NOK 9.5m

Financial health · 2025

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

Who owns KARL J SVENSEN AS?

KAY SVENSEN
KARL J SVENSEN AS
NOK 6.1m rev. · NOK 234,000 profit

KARL J SVENSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KARL J SVENSEN AS

Who owns KARL J SVENSEN AS?

KAY SVENSEN is the largest registered owner, with 100.0%.

What is the revenue of KARL J SVENSEN AS?

KARL J SVENSEN AS had revenue of NOK 6.1m in 2025.

Who is the general manager of KARL J SVENSEN AS?

Kay Svensen is registered as general manager of KARL J SVENSEN AS.

Where is KARL J SVENSEN AS based?

KARL J SVENSEN AS has its business address in Sandefjord.

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.