BIZTRAC BETA
COMPANY REGISTER PROFILE
834857332 ORG. NO. 2024 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Computer programming activities

GULLPASTILLEN HOLDING AS

Org. no. 834857332 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Equity NOK 30,000
Incorporated 2024
Share capital NOK 30,000

GULLPASTILLEN HOLDING AS is registered as a limited company in Bærum, Akershus with organisation number 834857332. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 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.”.

Key figures · 2024

Equity
NOK 30,000
Est. value
NOK 54,000

Financial health · 2024

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

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

Who owns GULLPASTILLEN HOLDING AS?

ANDREAS LUND
GULLPASTILLEN HOLDING AS

GULLPASTILLEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GULLPASTILLEN HOLDING AS own?

GULLPASTILLEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GULLPASTILLEN HOLDING AS

Who owns GULLPASTILLEN HOLDING AS?

ANDREAS LUND is the largest registered owner, with 100.0%.

Who is the general manager of GULLPASTILLEN HOLDING AS?

Andreas Lund is registered as general manager of GULLPASTILLEN HOLDING AS.

Where is GULLPASTILLEN HOLDING AS based?

GULLPASTILLEN HOLDING AS has its business address in Jar.

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.