BIZTRAC BETA
Rental and operating of own or leased real estate

GOGANI EIENDOM AS

Org. no. 931244817 Limited company (AS) Indre Fosen Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 392,000
Operating profit NOK 79,000
Equity NOK 4.1m
Incorporated 2023
Share capital NOK 144,000

GOGANI EIENDOM AS is registered as a limited company in Indre Fosen, Trøndelag with organisation number 931244817. 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 144,000, divided into 80 shares. The company's stated purpose is: “Erverve og drifte fast eiendom og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også tilby tannlegetjenester til tannklinikker.”. The most recent filed accounts, for the 2025 financial year, show NOK 392,000 in revenue and NOK 79,000 in operating profit.

Key figures · 2025

Revenue
NOK 392,000
Operating profit
NOK 79,000
Equity
NOK 4.1m
Est. value
NOK 3.0m

Financial health · 2025

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
66.3%
Very good
Equity as a share of total capital

Who owns GOGANI EIENDOM AS?

GOGANI HOLDING AS
GOGANI EIENDOM AS
NOK 392,000 rev. · NOK 79,000 profit

GOGANI EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GOGANI EIENDOM AS

Who owns GOGANI EIENDOM AS?

GOGANI HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of GOGANI EIENDOM AS?

GOGANI EIENDOM AS had revenue of NOK 392,000 in 2025.

Where is GOGANI EIENDOM AS based?

GOGANI EIENDOM AS has its business address in Rissa.

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.