BIZTRAC BETA
Intermediation service activities for non-specialised retail sale

GI BUD AS

Org. no. 916893949 Limited company (AS) Sola Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 772,000
Operating profit NOK −184,000
Equity NOK 20,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

GI BUD AS is registered as a limited company in Sola, Rogaland with organisation number 916893949. The business is classified under intermediation service activities for non-specialised retail sale (NACE 47.910). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av nettsider og annet som naturlig faller sammen med dette. Detaljhandel utenom butikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 772,000 in revenue and NOK −184,000 in operating profit.

Key figures · 2024

Revenue
NOK 772,000
Operating profit
NOK −184,000
Equity
NOK 20,000
Est. value
NOK 261,000

Financial health · 2024

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

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

Who owns GI BUD AS?

NORSTAMPS HOLDING AS
GI BUD AS
NOK 772,000 rev. · NOK −184,000 profit

GI BUD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GI BUD AS

Who owns GI BUD AS?

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

What is the revenue of GI BUD AS?

GI BUD AS had revenue of NOK 772,000 in 2024.

Who is the general manager of GI BUD AS?

John-Arne Paulsen is registered as general manager of GI BUD AS.

Where is GI BUD AS based?

GI BUD AS has its business address in Røyneberg.

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.