BIZTRAC BETA
Restaurant activities

INGELSTAD & STENSTAD EIENDOM AS

Org. no. 911960257 Limited company (AS) Seljord Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 781,000
Operating profit NOK 325,000
Equity NOK 4.3m
Incorporated 2013
Share capital NOK 30,000

INGELSTAD & STENSTAD EIENDOM AS is registered as a limited company in Seljord, Telemark with organisation number 911960257. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utleie av fast eiendom, eie fast eiendom, eiendomsutvikling, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 781,000 in revenue and NOK 325,000 in operating profit.

Key figures · 2024

Revenue
NOK 781,000
Operating profit
NOK 325,000
Equity
NOK 4.3m
Est. value
NOK 3.4m

Financial health · 2025

Liquidity
9.64
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
92.5%
Very good
Equity as a share of total capital

Who owns INGELSTAD & STENSTAD EIENDOM AS?

AARNESGRUPPEN HOLDING AS
INGELSTAD & STENSTAD EIENDOM AS
NOK 781,000 rev. · NOK 325,000 profit

INGELSTAD & STENSTAD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about INGELSTAD & STENSTAD EIENDOM AS

Who owns INGELSTAD & STENSTAD EIENDOM AS?

AARNESGRUPPEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of INGELSTAD & STENSTAD EIENDOM AS?

INGELSTAD & STENSTAD EIENDOM AS had revenue of NOK 781,000 in 2024.

Where is INGELSTAD & STENSTAD EIENDOM AS based?

INGELSTAD & STENSTAD EIENDOM AS has its business address in Seljord.

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.