biztrac. BETA
COMPANY REGISTER PROFILE
914276195 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

SEBPHI EIENDOM AS

Org. no. 914276195 Limited company (AS) Bærum Incorporated 2014 Active
Revenue 2025 NOK 8
Operating profit NOK −100,000
Equity NOK 258,000
Incorporated 2014
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−100k kr).

SEBPHI EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 914276195. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Eiendomsutvikling. Kjøp, salg og utleie av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 8 in revenue and NOK −100,000 in operating profit.

Key figures · 2025

Revenue
NOK 8
Operating profit
NOK −100,000
▼ −27 %
Equity
NOK 258,000
▼ −40 %
Est. value
NOK 235,000

Financial health · 2025

Liquidity
0.40
Not satisfactory
Current assets ÷ current liabilities
Profitability
-3.4%
Not satisfactory
Return on total assets
Solidity
10.6%
Satisfactory
Equity as a share of total capital

Who owns SEBPHI EIENDOM AS?

SEBPHI EIENDOM AS
NOK 8 rev. · NOK −100,000 profit

SEBPHI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEBPHI EIENDOM AS

Who owns SEBPHI EIENDOM AS?

OLSEN & KRISTENSEN LTD NUF is the largest registered owner, with 100.0%.

What is the revenue of SEBPHI EIENDOM AS?

SEBPHI EIENDOM AS had revenue of NOK 8 in 2025.

Who is the general manager of SEBPHI EIENDOM AS?

Gro Hege Kristensen is registered as general manager of SEBPHI EIENDOM AS.

Where is SEBPHI EIENDOM AS based?

SEBPHI EIENDOM AS has its business address in Haslum.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.