BIZTRAC BETA
Computer consultancy and computer facilities management activities

STACQ AS

Org. no. 932575442 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 13.8m
Operating profit NOK 882,000
Equity NOK 733,000
Incorporated 2023
Employees 15
Share capital NOK 30,000

STACQ AS is registered as a limited company in Oslo, Oslo with organisation number 932575442. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2023 and has 15 registered employees. 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 2024 financial year, show NOK 13.8m in revenue and NOK 882,000 in operating profit.

Key figures · 2024

Revenue
NOK 13.8m
Operating profit
NOK 882,000
Equity
NOK 733,000
Est. value
NOK 5.5m

Financial health · 2024

Liquidity
1.24
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 STACQ AS?

FATHERHOOD AS
STACQ AS
NOK 13.8m rev. · NOK 882,000 profit

STACQ AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STACQ AS own?

STACQ AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STACQ AS

Who owns STACQ AS?

FATHERHOOD AS is the largest registered owner, with 50.0%.

What is the revenue of STACQ AS?

STACQ AS had revenue of NOK 13.8m in 2024.

Who is the general manager of STACQ AS?

Thomas Eriksen is registered as general manager of STACQ AS.

Where is STACQ AS based?

STACQ 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 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.