BIZTRAC BETA
COMPANY REGISTER PROFILE
985656460 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Logging

STORE BJØRNSTAD AS

Org. no. 985656460 Limited company (AS) Halden Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 18.6m
Operating profit NOK 5.7m
Equity NOK 56.5m
Incorporated 2003
Share capital NOK 18.1m

STORE BJØRNSTAD AS is registered as a limited company in Halden, Østfold with organisation number 985656460. The business is classified under logging (NACE 02.200). The company was incorporated in 2003. Registered share capital is NOK 18.1m, divided into 100 shares. The company's stated purpose is: “Å drive jord- og skogbruk og tomte- og eiendomsutvikling, samt investere i aksjer og annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 18.6m in revenue and NOK 5.7m in operating profit.

Former names: FREDRIKSTEN BYGG AS

Key figures · 2025

Revenue
NOK 18.6m
Operating profit
NOK 5.7m
Equity
NOK 56.5m
Est. value
NOK 46.9m

Financial health · 2025

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

Who owns STORE BJØRNSTAD AS?

STORE BJØRNSTAD AS
NOK 18.6m rev. · NOK 5.7m profit

STORE BJØRNSTAD AS has 1 registered shareholder:

All shareholders and roles →

Group structure

STORE BJØRNSTAD AS er morselskap for 2 datterselskaper:

Frequently asked questions about STORE BJØRNSTAD AS

Who owns STORE BJØRNSTAD AS?

C-G HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of STORE BJØRNSTAD AS?

STORE BJØRNSTAD AS had revenue of NOK 18.6m in 2025.

Who is the general manager of STORE BJØRNSTAD AS?

Inger-Oline Garder is registered as general manager of STORE BJØRNSTAD AS.

Where is STORE BJØRNSTAD AS based?

STORE BJØRNSTAD AS has its business address in Tistedal.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.