BIZTRAC BETA
COMPANY REGISTER PROFILE
976192532 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Painting and glazing

SIGDESTAD & CO AS

Org. no. 976192532 Limited company (AS) Rakkestad Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 2.5m
Operating profit NOK 191,000
Equity NOK 1.7m
Incorporated 1996
Employees 5
Share capital NOK 100,000

SIGDESTAD & CO AS is registered as a limited company in Rakkestad, Østfold with organisation number 976192532. The business is classified under painting and glazing (NACE 43.340). The company was incorporated in 1996 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive malerfirma, samt deltagelse i andre selskaper og hva som dermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK 191,000 in operating profit.

Former names: HAN AS

Key figures · 2025

Revenue
NOK 2.5m
▼ −23 %
Operating profit
NOK 191,000
▲ +21 %
Equity
NOK 1.7m
▼ −9 %
Est. value
NOK 1.4m

Financial health · 2025

Liquidity
2.25
Very good
Current assets ÷ current liabilities
Profitability
6.0%
Satisfactory
Return on total assets
Solidity
60.5%
Very good
Equity as a share of total capital

Who owns SIGDESTAD & CO AS?

SIGDESTAD & CO AS
NOK 2.5m rev. · NOK 191,000 profit

SIGDESTAD & CO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SIGDESTAD & CO AS

Who owns SIGDESTAD & CO AS?

AAGE SIGDESTAD is the largest registered owner, with 100.0%.

What is the revenue of SIGDESTAD & CO AS?

SIGDESTAD & CO AS had revenue of NOK 2.5m in 2025.

Who is the general manager of SIGDESTAD & CO AS?

Aage Sigdestad is registered as general manager of SIGDESTAD & CO AS.

Where is SIGDESTAD & CO AS based?

SIGDESTAD & CO AS has its business address in Degernes.

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.