biztrac. BETA
COMPANY REGISTER PROFILE
917782369 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

STIKLESTAD EIENDOM NORDGATA AS

Org. no. 917782369 Limited company (AS) Levanger Incorporated 2016 Active
Operating profit NOK −11.5m
Equity NOK 106,000
Incorporated 2016
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−11,5 mill kr).

STIKLESTAD EIENDOM NORDGATA AS is registered as a limited company in Levanger, Trøndelag with organisation number 917782369. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2016. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Eiendoms- og handelsvirksomhet og hva hermed står i forbindelse, herunder ved aksjeinnskudd eller på annen måte å delta i andre foretak.”.

Former names: STIKLESTAD EIENDOM VEKTARGATA AS

Key figures · 2025

Operating profit
NOK −11.5m
▼ −20025 %
Equity
NOK 106,000
▲ +0 %
Est. value
NOK 108,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-29.4%
Not satisfactory
Return on total assets
Solidity
0.3%
Not satisfactory
Equity as a share of total capital

Who owns STIKLESTAD EIENDOM NORDGATA AS?

STIKLESTAD EIENDOM NORDGATA AS
· NOK −11.5m profit

STIKLESTAD EIENDOM NORDGATA AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STIKLESTAD EIENDOM NORDGATA AS er morselskap for 1 datterselskap:

Frequently asked questions about STIKLESTAD EIENDOM NORDGATA AS

Who owns STIKLESTAD EIENDOM NORDGATA AS?

STIKLESTAD EIENDOM AS is the largest registered owner, with 100.0%.

Where is STIKLESTAD EIENDOM NORDGATA AS based?

STIKLESTAD EIENDOM NORDGATA AS has its business address in Levanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

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