BIZTRAC BETA
Development of building projects

STIK 1 AS

Org. no. 914414806 Limited company (AS) Trondheim Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK −491,000
Equity NOK 901,000
Incorporated 2014
Share capital NOK 133,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−491k kr).

STIK 1 AS is registered as a limited company in Trondheim, Trøndelag with organisation number 914414806. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 133,000, divided into 66644 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder kjøp, salg, utvikling og drift av fast eiendom, deltagelse i andre selskaper samt annet som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK −491,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK −491,000
Equity
NOK 901,000
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns STIK 1 AS?

EIDCO AS
STIK 1 AS
NOK 3.5m rev. · NOK −491,000 profit

STIK 1 AS has 3 registered shareholders:

All shareholders and roles →

Which companies does STIK 1 AS own?

STIK 1 AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about STIK 1 AS

Who owns STIK 1 AS?

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

What is the revenue of STIK 1 AS?

STIK 1 AS had revenue of NOK 3.5m in 2024.

Who is the general manager of STIK 1 AS?

Per Arne Eide is registered as general manager of STIK 1 AS.

Where is STIK 1 AS based?

STIK 1 AS has its business address in Trondheim.

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.