BIZTRAC BETA
Uoppgitt

BIGFROG AS

Org. no. 915557287 Limited company (AS) Sandefjord Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 11,000
Incorporated 2015
Share capital NOK 30,000

Signals

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

BIGFROG AS is registered as a limited company in Sandefjord, Vestfold with organisation number 915557287. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investeringer i ulike type selskap og 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 foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 11,000
Est. value
NOK 21.7m

Financial health · 2025

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

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

Who owns BIGFROG AS?

GEIR FREDDY KRISTIANSEN
BIGFROG AS
NOK 0 rev. · NOK −16,000 profit

BIGFROG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BIGFROG AS own?

BIGFROG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BIGFROG AS

Who owns BIGFROG AS?

GEIR FREDDY KRISTIANSEN is the largest registered owner, with 100.0%.

What is the revenue of BIGFROG AS?

BIGFROG AS had revenue of NOK 0 in 2024.

Where is BIGFROG AS based?

BIGFROG AS has its business address in Sandefjord.

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.