BIZTRAC BETA
Raising of animals n.e.c.

GAMLE FREDRIKSTAD BIGÅRD AS

Org. no. 932463601 Limited company (AS) Fredrikstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 121,000
Operating profit NOK 9,000
Equity NOK 111,000
Incorporated 2023
Share capital NOK 100,000

GAMLE FREDRIKSTAD BIGÅRD AS is registered as a limited company in Fredrikstad, Østfold with organisation number 932463601. The business is classified under raising of animals n.e.c. (NACE 01.489). The company was incorporated in 2023. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Bigård, biavl, produksjon av honning og voks. Kjøp og salg av dronninger, avleggere og utstyr, pluss alt innen birøkt.”. The most recent filed accounts, for the 2025 financial year, show NOK 121,000 in revenue and NOK 9,000 in operating profit.

Key figures · 2025

Revenue
NOK 121,000
Operating profit
NOK 9,000
Equity
NOK 111,000
Est. value
NOK 95,000

Financial health · 2025

Liquidity
3.73
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
73.2%
Very good
Equity as a share of total capital

Who owns GAMLE FREDRIKSTAD BIGÅRD AS?

TORE BRENNA
GAMLE FREDRIKSTAD BIGÅRD AS
NOK 121,000 rev. · NOK 9,000 profit

GAMLE FREDRIKSTAD BIGÅRD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about GAMLE FREDRIKSTAD BIGÅRD AS

Who owns GAMLE FREDRIKSTAD BIGÅRD AS?

TORE BRENNA is the largest registered owner, with 100.0%.

What is the revenue of GAMLE FREDRIKSTAD BIGÅRD AS?

GAMLE FREDRIKSTAD BIGÅRD AS had revenue of NOK 121,000 in 2025.

Who is the general manager of GAMLE FREDRIKSTAD BIGÅRD AS?

Tore Brenna is registered as general manager of GAMLE FREDRIKSTAD BIGÅRD AS.

Where is GAMLE FREDRIKSTAD BIGÅRD AS based?

GAMLE FREDRIKSTAD BIGÅRD AS has its business address in Gamle Fredrikstad.

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.