BIZTRAC BETA
Rental and operating of own or leased real estate

SEGLA EIENDOM AS

Org. no. 936905331 Limited company (AS) Senja Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 18,000
Incorporated 2025
Share capital NOK 30,000

Signals

1 flags
  • Nystiftet selskap Selskapet ble stiftet 2025-12-17.

SEGLA EIENDOM AS is registered as a limited company in Senja, Troms with organisation number 936905331. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering i fast eiendom, herunder kjøp, salg, leie og utleie av fast eiendom og alt som for øvrig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 18,000
Est. value
NOK 16,000

Financial health · 2025

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

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

Who owns SEGLA EIENDOM AS?

SEGLA INVEST AS
SEGLA EIENDOM AS
NOK 0 rev. · NOK 0 profit

SEGLA EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEGLA EIENDOM AS

Who owns SEGLA EIENDOM AS?

SEGLA INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of SEGLA EIENDOM AS?

SEGLA EIENDOM AS had revenue of NOK 0 in 2025.

Who is the general manager of SEGLA EIENDOM AS?

Remi Berntsen is registered as general manager of SEGLA EIENDOM AS.

Where is SEGLA EIENDOM AS based?

SEGLA EIENDOM AS has its business address in Fjordgard.

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.