BIZTRAC BETA
Joinery installation

GD KJØKKEN MONTERING AS

Org. no. 933565882 Limited company (AS) Eidsvoll Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK −31,000
Equity NOK 104,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).

GD KJØKKEN MONTERING AS is registered as a limited company in Eidsvoll, Akershus with organisation number 933565882. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Montering av kjøkken, snekkerarbeid, og andre tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK −31,000
Equity
NOK 104,000
Est. value
NOK 491,000

Financial health · 2025

Liquidity
1.57
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.5%
Good
Equity as a share of total capital

Who owns GD KJØKKEN MONTERING AS?

GYTAUTAS DAUGINAS
GD KJØKKEN MONTERING AS
NOK 1.3m rev. · NOK −31,000 profit

GD KJØKKEN MONTERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GD KJØKKEN MONTERING AS

Who owns GD KJØKKEN MONTERING AS?

GYTAUTAS DAUGINAS is the largest registered owner, with 100.0%.

What is the revenue of GD KJØKKEN MONTERING AS?

GD KJØKKEN MONTERING AS had revenue of NOK 1.3m in 2025.

Who is the general manager of GD KJØKKEN MONTERING AS?

Gytautas Dauginas is registered as general manager of GD KJØKKEN MONTERING AS.

Where is GD KJØKKEN MONTERING AS based?

GD KJØKKEN MONTERING AS has its business address in Råholt.

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.