BIZTRAC BETA
Construction of residential and non-residential buildings

BRØDRENE FAANE AS

Org. no. 961335833 Limited company (AS) Hjartdal Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 29,000
Incorporated 1991
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

BRØDRENE FAANE AS is registered as a limited company in Hjartdal, Telemark with organisation number 961335833. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 1991. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Tømrervirksomhet og hva herved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 29,000
Est. value
NOK 29,000

Financial health · 2025

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

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

Who owns BRØDRENE FAANE AS?

ODD ARNE FAANE
BRØDRENE FAANE AS
NOK 0 rev. · NOK −10,000 profit

BRØDRENE FAANE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BRØDRENE FAANE AS

Who owns BRØDRENE FAANE AS?

ODD ARNE FAANE is the largest registered owner, with 50.0%.

What is the revenue of BRØDRENE FAANE AS?

BRØDRENE FAANE AS had revenue of NOK 0 in 2025.

Who is the general manager of BRØDRENE FAANE AS?

Odd Arne Faane is registered as general manager of BRØDRENE FAANE AS.

Where is BRØDRENE FAANE AS based?

BRØDRENE FAANE AS has its business address in Sauland.

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.