BIZTRAC BETA
Computer consultancy and computer facilities management activities

4CIS CONSULTING AS

Org. no. 931596446 Limited company (AS) Hole Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 622,000
Equity NOK 354,000
Incorporated 2023
Share capital NOK 30,000

4CIS CONSULTING AS is registered as a limited company in Hole, Buskerud with organisation number 931596446. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen IT og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 622,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 622,000
Equity
NOK 354,000
Est. value
NOK 3.8m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.6%
Good
Equity as a share of total capital

Who owns 4CIS CONSULTING AS?

ULF JOHAN STØA
4CIS CONSULTING AS
NOK 3.3m rev. · NOK 622,000 profit

4CIS CONSULTING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about 4CIS CONSULTING AS

Who owns 4CIS CONSULTING AS?

ULF JOHAN STØA is the largest registered owner, with 100.0%.

What is the revenue of 4CIS CONSULTING AS?

4CIS CONSULTING AS had revenue of NOK 3.3m in 2025.

Who is the general manager of 4CIS CONSULTING AS?

Ulf Johan Støa is registered as general manager of 4CIS CONSULTING AS.

Where is 4CIS CONSULTING AS based?

4CIS CONSULTING AS has its business address in Røyse.

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.