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

SANVARM AS

Org. no. 977245508 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2025 NOK 213,000
Operating profit NOK −116,000
Equity NOK 1.9m
Incorporated 1997
Share capital NOK 186,000

Signals

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

SANVARM AS is registered as a limited company in Oslo, Oslo with organisation number 977245508. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1997. Registered share capital is NOK 186,000, divided into 31 shares. The company's stated purpose is: “Rørleggervirksomhet og handel samt hva hermed står i naturlig forbindelse, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 213,000 in revenue and NOK −116,000 in operating profit.

Former names: SANITÆR OG VARMEVAKTA AS

Key figures · 2025

Revenue
NOK 213,000
▼ −79 %
Operating profit
NOK −116,000
▼ −134 %
Equity
NOK 1.9m
▼ −22 %
Est. value
NOK 893,000

Financial health · 2025

Liquidity
7.07
Very good
Current assets ÷ current liabilities
Profitability
-2.8%
Not satisfactory
Return on total assets
Solidity
88.0%
Very good
Equity as a share of total capital

Who owns SANVARM AS?

SANVARM AS
NOK 213,000 rev. · NOK −116,000 profit

SANVARM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANVARM AS

Who owns SANVARM AS?

Kåre Haukåssveen is the largest registered owner, with 100.0%.

What is the revenue of SANVARM AS?

SANVARM AS had revenue of NOK 213,000 in 2025.

Who is the general manager of SANVARM AS?

Kåre Haukåssveen is registered as general manager of SANVARM AS.

Where is SANVARM AS based?

SANVARM AS has its business address in Oslo.

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.