BIZTRAC BETA
Development of building projects

JUST BROCHSGATE 12 EIENDOM AS

Org. no. 917238502 Limited company (AS) Hamar Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 181,000
Operating profit NOK 81,000
Equity NOK 95,000
Incorporated 2016
Share capital NOK 30,000

JUST BROCHSGATE 12 EIENDOM AS is registered as a limited company in Hamar, Innlandet with organisation number 917238502. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eiendomsutvikling.”. The most recent filed accounts, for the 2024 financial year, show NOK 181,000 in revenue and NOK 81,000 in operating profit.

Key figures · 2024

Revenue
NOK 181,000
Operating profit
NOK 81,000
Equity
NOK 95,000
Est. value
NOK 100,000

Financial health · 2024

Liquidity
-2.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
6.3%
Weak
Equity as a share of total capital

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

Who owns JUST BROCHSGATE 12 EIENDOM AS?

ERIK JENDAL
JUST BROCHSGATE 12 EIENDOM AS
NOK 181,000 rev. · NOK 81,000 profit

JUST BROCHSGATE 12 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about JUST BROCHSGATE 12 EIENDOM AS

Who owns JUST BROCHSGATE 12 EIENDOM AS?

ERIK JENDAL is the largest registered owner, with 100.0%.

What is the revenue of JUST BROCHSGATE 12 EIENDOM AS?

JUST BROCHSGATE 12 EIENDOM AS had revenue of NOK 181,000 in 2024.

Who is the general manager of JUST BROCHSGATE 12 EIENDOM AS?

Erik Jendal is registered as general manager of JUST BROCHSGATE 12 EIENDOM AS.

Where is JUST BROCHSGATE 12 EIENDOM AS based?

JUST BROCHSGATE 12 EIENDOM AS has its business address in Hamar.

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.