BIZTRAC BETA
Uoppgitt

GULLEIK AS

Org. no. 930536415 Limited company (AS) Eidsvoll Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −3,000
Equity NOK 44,000
Incorporated 2022
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−3k kr).

GULLEIK AS is registered as a limited company in Eidsvoll, Akershus with organisation number 930536415. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −3,000
Equity
NOK 44,000
Est. value
NOK 52,000

Financial health · 2024

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

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

Who owns GULLEIK AS?

JON GULLEIK GRÆE
GULLEIK AS
NOK 0 rev. · NOK −3,000 profit

GULLEIK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GULLEIK AS own?

GULLEIK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GULLEIK AS

Who owns GULLEIK AS?

JON GULLEIK GRÆE is the largest registered owner, with 100.0%.

What is the revenue of GULLEIK AS?

GULLEIK AS had revenue of NOK 0 in 2024.

Where is GULLEIK AS based?

GULLEIK 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.