BIZTRAC BETA
Business and other management consultancy activities

CONNECTING SERVICES AS

Org. no. 917717273 Limited company (AS) Stavanger Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 527,000
Equity NOK 508,000
Incorporated 2016
Share capital NOK 125,000

CONNECTING SERVICES AS is registered as a limited company in Stavanger, Rogaland with organisation number 917717273. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2016. Registered share capital is NOK 125,000, divided into 125 shares. The company's stated purpose is: “Salg av rådgivningstjenester innen økonomi og informasjonsteknologi, investeringer i andre selskap av enhver art, samt kjøp, salg og utleie av eiendom. Selskapets virksomhet er også tannhelsetjenester, samt alt som står i naturlig sammenheng med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 527,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 527,000
Equity
NOK 508,000
Est. value
NOK 2.0m

Financial health · 2025

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

Who owns CONNECTING SERVICES AS?

CONNECTING BUSINESS AS
CONNECTING SERVICES AS
NOK 1.3m rev. · NOK 527,000 profit

CONNECTING SERVICES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CONNECTING SERVICES AS

Who owns CONNECTING SERVICES AS?

CONNECTING BUSINESS AS is the largest registered owner, with 100.0%.

What is the revenue of CONNECTING SERVICES AS?

CONNECTING SERVICES AS had revenue of NOK 1.3m in 2025.

Where is CONNECTING SERVICES AS based?

CONNECTING SERVICES AS has its business address in Stavanger.

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.