BIZTRAC BETA
Development of building projects

INGRIDTJØNNA EIENDOM AS

Org. no. 918984259 Limited company (AS) Selbu Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 27,000
Incorporated 2017
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

INGRIDTJØNNA EIENDOM AS is registered as a limited company in Selbu, Trøndelag with organisation number 918984259. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og opparbeiding av tomter.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 27,000
Est. value
NOK 25,000

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns INGRIDTJØNNA EIENDOM AS?

SIRI SVENDGÅRD-STOKKE
INGRIDTJØNNA EIENDOM AS
NOK 0 rev. · NOK −8,000 profit

INGRIDTJØNNA EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about INGRIDTJØNNA EIENDOM AS

Who owns INGRIDTJØNNA EIENDOM AS?

SIRI SVENDGÅRD-STOKKE is the largest registered owner, with 50.0%.

What is the revenue of INGRIDTJØNNA EIENDOM AS?

INGRIDTJØNNA EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of INGRIDTJØNNA EIENDOM AS?

Magne Svendgård is registered as general manager of INGRIDTJØNNA EIENDOM AS.

Where is INGRIDTJØNNA EIENDOM AS based?

INGRIDTJØNNA EIENDOM AS has its business address in Selbu.

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.