biztrac. BETA
COMPANY REGISTER PROFILE
835153312 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Repair and maintenance of electronic and optical equipment

HWCS AS

Org. no. 835153312 Limited company (AS) Ullensvang Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −7,000
Equity NOK 17,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

HWCS AS is registered as a limited company in Ullensvang, Vestland with organisation number 835153312. The business is classified under repair and maintenance of electronic and optical equipment (NACE 33.130). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Konsulent og servicetjenester på elektromekanisk utstyr. Kjøp og salg av elektromekanisk utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −7,000
Equity
NOK 17,000
Est. value
NOK 20,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HWCS AS?

HWCS AS
NOK 0 rev. · NOK −7,000 profit

HWCS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HWCS AS

Who owns HWCS AS?

Håvard Waagen is the largest registered owner, with 100.0%.

What is the revenue of HWCS AS?

HWCS AS had revenue of NOK 0 in 2025.

Who is the general manager of HWCS AS?

Håvard Waagen is registered as general manager of HWCS AS.

Where is HWCS AS based?

HWCS AS has its business address in Odda.

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.