BIZTRAC BETA
Roofing activities

SIGFRED BENTZEN & SØNN AS

Org. no. 910462105 Limited company (AS) Oslo Incorporated 1963 Active
Ownership graph ↗
Revenue 2025 NOK 26.3m
Operating profit NOK −988,000
Equity NOK 4.6m
Incorporated 1963
Employees 21
Share capital NOK 108,000

Signals

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

SIGFRED BENTZEN & SØNN AS is registered as a limited company in Oslo, Oslo with organisation number 910462105. The business is classified under roofing activities (NACE 43.410). The company was incorporated in 1963 and has 21 registered employees. Registered share capital is NOK 108,000, divided into 18 shares. The company's stated purpose is: “Blikkenslagerarbeid.”. The most recent filed accounts, for the 2025 financial year, show NOK 26.3m in revenue and NOK −988,000 in operating profit.

Key figures · 2025

Revenue
NOK 26.3m
Operating profit
NOK −988,000
Equity
NOK 4.6m
Est. value
NOK 11.1m

Financial health · 2025

Liquidity
1.05
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.8%
Good
Equity as a share of total capital

Who owns SIGFRED BENTZEN & SØNN AS?

JAN-ERIK BENTZEN
SIGFRED BENTZEN & SØNN AS
NOK 26.3m rev. · NOK −988,000 profit

SIGFRED BENTZEN & SØNN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIGFRED BENTZEN & SØNN AS

Who owns SIGFRED BENTZEN & SØNN AS?

JAN-ERIK BENTZEN is the largest registered owner, with 100.0%.

What is the revenue of SIGFRED BENTZEN & SØNN AS?

SIGFRED BENTZEN & SØNN AS had revenue of NOK 26.3m in 2025.

Who is the general manager of SIGFRED BENTZEN & SØNN AS?

Jan-Erik Bentzen is registered as general manager of SIGFRED BENTZEN & SØNN AS.

Where is SIGFRED BENTZEN & SØNN AS based?

SIGFRED BENTZEN & SØNN AS has its business address in Oslo.

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.