BIZTRAC BETA
Norwegian company

FURBERG HOLDING AS

Org. no. 963014325 Limited company (AS) Frøya Incorporated 1991 Active
Ownership graph ↗
Revenue 2024 NOK 100,000
Operating profit NOK −333,000
Equity NOK 5.1m
Incorporated 1991
Share capital NOK 170,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−333k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

FURBERG HOLDING AS is registered as a limited company in Frøya, Trøndelag with organisation number 963014325. The company was incorporated in 1991. Registered share capital is NOK 170,000, divided into 170 shares. The company's stated purpose is: “Kjøp av aksjer eller på annen måte være engasjert i annen næringsvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 100,000 in revenue and NOK −333,000 in operating profit.

Key figures · 2024

Revenue
NOK 100,000
Operating profit
NOK −333,000
Equity
NOK 5.1m
Est. value
NOK 2.8m

Financial health · 2024

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

Who owns FURBERG HOLDING AS?

Furberg & Sønn A/S
FURBERG HOLDING AS
NOK 100,000 rev. · NOK −333,000 profit

FURBERG HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FURBERG HOLDING AS

Who owns FURBERG HOLDING AS?

Furberg & Sønn A/S is the largest registered owner, with 98.8%.

What is the revenue of FURBERG HOLDING AS?

FURBERG HOLDING AS had revenue of NOK 100,000 in 2024.

Who is the general manager of FURBERG HOLDING AS?

Geir Karsten Furberg is registered as general manager of FURBERG HOLDING AS.

Where is FURBERG HOLDING AS based?

FURBERG HOLDING AS has its business address in Dyrvik.

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.