BIZTRAC BETA
Development of building projects

HUSEBY SAG AS

Org. no. 914014727 Limited company (AS) Fredrikstad Incorporated 2014 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK −37,000
Incorporated 2014
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−37k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−21k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HUSEBY SAG AS is registered as a limited company in Fredrikstad, Østfold with organisation number 914014727. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Sagbruksvirksomhet med nisjeproduksjon fra store rotstokker som råstoff av furu, som i dag ikke er et foretrukket valg som råstoff til industriell stor skala virksomhet.”.

Key figures · 2025

Operating profit
NOK −21,000
Equity
NOK −37,000

Financial health · 2025

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

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

Who owns HUSEBY SAG AS?

PLANKEBYEN NÆRINGSPARK AS
HUSEBY SAG AS
· NOK −21,000 profit

HUSEBY SAG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUSEBY SAG AS

Who owns HUSEBY SAG AS?

PLANKEBYEN NÆRINGSPARK AS is the largest registered owner, with 100.0%.

Who is the general manager of HUSEBY SAG AS?

Terje Gjølberg is registered as general manager of HUSEBY SAG AS.

Where is HUSEBY SAG AS based?

HUSEBY SAG AS has its business address in 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.