BIZTRAC BETA
Rental and operating of own or leased real estate

STENBERG EIENDOM AS

Org. no. 963944691 Limited company (AS) Gran Incorporated 1992 Active
Ownership graph ↗
Revenue 2024 NOK 80,000
Operating profit NOK −2,000
Equity NOK 633,000
Incorporated 1992
Share capital NOK 200,000

Signals

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

STENBERG EIENDOM AS is registered as a limited company in Gran, Innlandet with organisation number 963944691. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1992. Registered share capital is NOK 200,000. The company's stated purpose is: “Kjøp, salg og utleie av faste eiendommer samt virksomhet som naturlig hører inn under det samme.”. The most recent filed accounts, for the 2024 financial year, show NOK 80,000 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 80,000
Operating profit
NOK −2,000
Equity
NOK 633,000
Est. value
NOK 493,000

Financial health · 2024

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

Who owns STENBERG EIENDOM AS?

HANS VIDAR STENBERG
STENBERG EIENDOM AS
NOK 80,000 rev. · NOK −2,000 profit

STENBERG EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STENBERG EIENDOM AS

Who owns STENBERG EIENDOM AS?

HANS VIDAR STENBERG is the largest registered owner, with 50.0%.

What is the revenue of STENBERG EIENDOM AS?

STENBERG EIENDOM AS had revenue of NOK 80,000 in 2024.

Who is the general manager of STENBERG EIENDOM AS?

Hans Vidar Stenberg is registered as general manager of STENBERG EIENDOM AS.

Where is STENBERG EIENDOM AS based?

STENBERG EIENDOM AS has its business address in Gran.

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.