BIZTRAC BETA
Rental and operating of own or leased real estate

GAUS DOKKA AS

Org. no. 921131771 Limited company (AS) Lillehammer Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 1.9m
Operating profit NOK 1.2m
Equity NOK 3.8m
Incorporated 2018
Share capital NOK 373,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

GAUS DOKKA AS is registered as a limited company in Lillehammer, Innlandet with organisation number 921131771. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 373,000, divided into 100 shares. The company's stated purpose is: “Eie og forestå drift av forretningseiendommer samt tilknyttet næringsvirksomhet og annen virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.9m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 1.9m
Operating profit
NOK 1.2m
Equity
NOK 3.8m
Est. value
NOK 5.4m

Financial health · 2024

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

Who owns GAUS DOKKA AS?

SEIELSTAD HOLDING AS
GAUS DOKKA AS
NOK 1.9m rev. · NOK 1.2m profit

GAUS DOKKA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAUS DOKKA AS

Who owns GAUS DOKKA AS?

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

What is the revenue of GAUS DOKKA AS?

GAUS DOKKA AS had revenue of NOK 1.9m in 2024.

Who is the general manager of GAUS DOKKA AS?

Åge Erling Melbø is registered as general manager of GAUS DOKKA AS.

Where is GAUS DOKKA AS based?

GAUS DOKKA AS has its business address in Lillehammer.

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.