BIZTRAC BETA
Rental and operating of own or leased real estate

JISER EIENDOM AS

Org. no. 986767436 Limited company (AS) Bømlo Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 1.3m
Equity NOK 4.5m
Incorporated 2004
Share capital NOK 500,000

JISER EIENDOM AS is registered as a limited company in Bømlo, Vestland with organisation number 986767436. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2004. Registered share capital is NOK 500,000, divided into 1000 shares. The company's stated purpose is: “Drift og utleie av fast eiendom, samt virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 1.3m
Equity
NOK 4.5m
Est. value
NOK 5.8m

Financial health · 2024

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

Who owns JISER EIENDOM AS?

ROBERT MIKAL STEINSBØ
JISER EIENDOM AS
NOK 2.0m rev. · NOK 1.3m profit

JISER EIENDOM AS has 6 registered shareholders:

All shareholders and roles →

Which companies does JISER EIENDOM AS own?

JISER EIENDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about JISER EIENDOM AS

Who owns JISER EIENDOM AS?

ROBERT MIKAL STEINSBØ is the largest registered owner, with 17.5%.

What is the revenue of JISER EIENDOM AS?

JISER EIENDOM AS had revenue of NOK 2.0m in 2024.

Who is the general manager of JISER EIENDOM AS?

Sigmund Inge Steinsbø is registered as general manager of JISER EIENDOM AS.

Where is JISER EIENDOM AS based?

JISER EIENDOM AS has its business address in Bremnes.

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.