BIZTRAC BETA
Rental and operating of own or leased real estate

B23 EIENDOM AS

Org. no. 933422631 Limited company (AS) Klepp Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.9m
Operating profit NOK 1.5m
Equity NOK 1.6m
Incorporated 2024
Share capital NOK 500,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

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

Key figures · 2025

Revenue
NOK 1.9m
Operating profit
NOK 1.5m
Equity
NOK 1.6m
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
0.64
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.0%
Weak
Equity as a share of total capital

Who owns B23 EIENDOM AS?

GRUDE & KLINGSHEIM EIENDOM AS
B23 EIENDOM AS
NOK 1.9m rev. · NOK 1.5m profit

B23 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about B23 EIENDOM AS

Who owns B23 EIENDOM AS?

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

What is the revenue of B23 EIENDOM AS?

B23 EIENDOM AS had revenue of NOK 1.9m in 2025.

Who is the general manager of B23 EIENDOM AS?

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

Where is B23 EIENDOM AS based?

B23 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.