BIZTRAC BETA
Business and other management consultancy activities

GULA INVEST AS

Org. no. 930831344 Limited company (AS) Frogn Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 47,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

GULA INVEST AS is registered as a limited company in Frogn, Akershus with organisation number 930831344. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby bedriftsrådgivning og konsulentbistand, samt direkte og indirekte deltakelse i selskaper med lignende eller annet formål”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 47,000
Est. value
NOK 244,000

Financial health · 2025

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

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

Who owns GULA INVEST AS?

GUNNAR LARSEN
GULA INVEST AS
NOK 0 rev. · NOK −8,000 profit

GULA INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GULA INVEST AS own?

GULA INVEST AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about GULA INVEST AS

Who owns GULA INVEST AS?

GUNNAR LARSEN is the largest registered owner, with 100.0%.

What is the revenue of GULA INVEST AS?

GULA INVEST AS had revenue of NOK 0 in 2025.

Where is GULA INVEST AS based?

GULA INVEST AS has its business address in Drøbak.

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.