BIZTRAC BETA
Rental and operating of own or leased real estate

B26 EIENDOM AS

Org. no. 928288412 Limited company (AS) Klepp Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 8.5m
Operating profit NOK 6.5m
Equity NOK 2.7m
Incorporated 2021
Share capital NOK 200,000

B26 EIENDOM AS is registered as a limited company in Klepp, Rogaland with organisation number 928288412. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Kjøp, utleie og salg av egen fast eiendom, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.5m in revenue and NOK 6.5m in operating profit.

Key figures · 2024

Revenue
NOK 8.5m
Operating profit
NOK 6.5m
Equity
NOK 2.7m
Est. value
NOK 5.6m

Financial health · 2024

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

Who owns B26 EIENDOM AS?

GRUDE & KLINGSHEIM EIENDOM AS
B26 EIENDOM AS
NOK 8.5m rev. · NOK 6.5m profit

B26 EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Which companies does B26 EIENDOM AS own?

B26 EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about B26 EIENDOM AS

Who owns B26 EIENDOM AS?

GRUDE & KLINGSHEIM EIENDOM AS is the largest registered owner, with 50.0%.

What is the revenue of B26 EIENDOM AS?

B26 EIENDOM AS had revenue of NOK 8.5m in 2024.

Who is the general manager of B26 EIENDOM AS?

Per Klingsheim is registered as general manager of B26 EIENDOM AS.

Where is B26 EIENDOM AS based?

B26 EIENDOM AS has its business address in Klepp Stasjon.

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.