BIZTRAC BETA
Buying and selling of own real estate

SELSBAKK EIENDOM AS

Org. no. 984673116 Limited company (AS) Trondheim Incorporated 2002 Active
Ownership graph ↗
Revenue 2025 NOK 3.6m
Operating profit NOK 302,000
Equity NOK −3.1m
Incorporated 2002
Share capital NOK 114,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−3,1 mill kr).

SELSBAKK EIENDOM AS is registered as a limited company in Trondheim, Trøndelag with organisation number 984673116. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2002. Registered share capital is NOK 114,000, divided into 100 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av fast eiendom, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.6m in revenue and NOK 302,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.6m
Operating profit
NOK 302,000
Equity
NOK −3.1m
Est. value
NOK 3.2m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SELSBAKK EIENDOM AS?

JACTA AS
SELSBAKK EIENDOM AS
NOK 3.6m rev. · NOK 302,000 profit

SELSBAKK EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SELSBAKK EIENDOM AS

Who owns SELSBAKK EIENDOM AS?

JACTA AS is the largest registered owner, with 100.0%.

What is the revenue of SELSBAKK EIENDOM AS?

SELSBAKK EIENDOM AS had revenue of NOK 3.6m in 2025.

Who is the general manager of SELSBAKK EIENDOM AS?

John Egil Myhre is registered as general manager of SELSBAKK EIENDOM AS.

Where is SELSBAKK EIENDOM AS based?

SELSBAKK EIENDOM AS has its business address in Trondheim.

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.