BIZTRAC BETA
Rental and operating of own or leased real estate

BORSHEIM EIENDOM AS

Org. no. 976291905 Limited company (AS) Sandnes Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 60,000
Operating profit NOK −2.3m
Equity NOK 66.1m
Incorporated 1996
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,3 mill kr).

BORSHEIM EIENDOM AS is registered as a limited company in Sandnes, Rogaland with organisation number 976291905. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 200,000, divided into 8000 shares. The company's stated purpose is: “Eie og utleie faste eiendommer samt delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 60,000 in revenue and NOK −2.3m in operating profit.

Key figures · 2024

Revenue
NOK 60,000
Operating profit
NOK −2.3m
Equity
NOK 66.1m
Est. value
NOK 45.3m

Financial health · 2024

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

Who owns BORSHEIM EIENDOM AS?

LEIF SVEIN BORSHEIM
BORSHEIM EIENDOM AS
NOK 60,000 rev. · NOK −2.3m profit

BORSHEIM EIENDOM AS has 6 registered shareholders:

All shareholders and roles →

Which companies does BORSHEIM EIENDOM AS own?

BORSHEIM EIENDOM AS holds stakes in 7 companies:

See the full ownership structure →

Frequently asked questions about BORSHEIM EIENDOM AS

Who owns BORSHEIM EIENDOM AS?

LEIF SVEIN BORSHEIM is the largest registered owner, with 42.5%.

What is the revenue of BORSHEIM EIENDOM AS?

BORSHEIM EIENDOM AS had revenue of NOK 60,000 in 2024.

Where is BORSHEIM EIENDOM AS based?

BORSHEIM EIENDOM AS has its business address in Sandnes.

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.