BIZTRAC BETA
Business and other management consultancy activities

CONNECTING AS

Org. no. 932927217 Limited company (AS) Askøy Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 171,000
Equity NOK −213,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−213k kr).

CONNECTING AS is registered as a limited company in Askøy, Vestland with organisation number 932927217. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Konsulentvirksomhet, samt deltakelse i annen tilknyttet virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 171,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.5m
Operating profit
NOK 171,000
Equity
NOK −213,000
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
0.16
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-239.0%
Weak
Equity as a share of total capital

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

Who owns CONNECTING AS?

GUNNHILD JOHANNE KVALVIK
CONNECTING AS
NOK 1.5m rev. · NOK 171,000 profit

CONNECTING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does CONNECTING AS own?

CONNECTING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CONNECTING AS

Who owns CONNECTING AS?

GUNNHILD JOHANNE KVALVIK is the largest registered owner, with 80.0%.

What is the revenue of CONNECTING AS?

CONNECTING AS had revenue of NOK 1.5m in 2025.

Where is CONNECTING AS based?

CONNECTING AS has its business address in Hauglandshella.

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.