BIZTRAC BETA
Rental and operating of own or leased real estate

GULENSKYSS EIGEDOM AS

Org. no. 929055535 Limited company (AS) Bergen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.4m
Operating profit NOK 559,000
Equity NOK −884,000
Incorporated 2022
Share capital NOK 500,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−884k kr).
  • Nylig endring 2026-02-03 Aksjekapital registrert 2026-02-03.

GULENSKYSS EIGEDOM AS is registered as a limited company in Bergen, Vestland with organisation number 929055535. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 500,000, divided into 100000 shares. The company's stated purpose is: “Investeringer i eiendom og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.4m in revenue and NOK 559,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.4m
Operating profit
NOK 559,000
Equity
NOK −884,000
Est. value
NOK 3.8m

Financial health · 2025

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

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

Who owns GULENSKYSS EIGEDOM AS?

GULENSKYSS AS
GULENSKYSS EIGEDOM AS
NOK 1.4m rev. · NOK 559,000 profit

GULENSKYSS EIGEDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GULENSKYSS EIGEDOM AS

Who owns GULENSKYSS EIGEDOM AS?

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

What is the revenue of GULENSKYSS EIGEDOM AS?

GULENSKYSS EIGEDOM AS had revenue of NOK 1.4m in 2025.

Where is GULENSKYSS EIGEDOM AS based?

GULENSKYSS EIGEDOM AS has its business address in Loddefjord.

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.