biztrac. BETA
COMPANY REGISTER PROFILE
932052466 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

TRYGGERE EIENDOM AS

Org. no. 932052466 Limited company (AS) Ålesund Incorporated 2023 Active
Revenue 2025 NOK 901,000
Operating profit NOK −46,000
Equity NOK −188,000
Incorporated 2023
Share capital NOK 200,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−188k kr).

TRYGGERE EIENDOM AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 932052466. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 200,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg, utleie og rehabilitering av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 901,000 in revenue and NOK −46,000 in operating profit.

Key figures · 2025

Revenue
NOK 901,000
▲ +415 %
Operating profit
NOK −46,000
▼ −147 %
Equity
NOK −188,000
▼ −169 %
Est. value
NOK 60,000

Financial health · 2025

Liquidity
46.38
Very good
Current assets ÷ current liabilities
Profitability
0.1%
Not satisfactory
Return on total assets
Solidity
-1.1%
Weak
Equity as a share of total capital

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

Who owns TRYGGERE EIENDOM AS?

TRYGGERE EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRYGGERE EIENDOM AS

Who owns TRYGGERE EIENDOM AS?

SPERREFISH AS is the largest registered owner, with 52.0%.

What is the revenue of TRYGGERE EIENDOM AS?

TRYGGERE EIENDOM AS had revenue of NOK 901,000 in 2025.

Where is TRYGGERE EIENDOM AS based?

TRYGGERE EIENDOM AS has its business address in Ellingsøy.

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.