BIZTRAC BETA
Activities of advertising agencies

SYGARD FOUGNER HOLDING AS

Org. no. 917885265 Limited company (AS) Lillehammer Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −5,000
Equity NOK 219,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

SYGARD FOUGNER HOLDING AS is registered as a limited company in Lillehammer, Innlandet with organisation number 917885265. The business is classified under activities of advertising agencies (NACE 73.110). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Forvalte sine eierinteresser, foreta finansielle og industrielle investeringer og tilby administrative tjenester, samt all annen virksomhet som henger naturlig sammen med dette.”.

Key figures · 2024

Operating profit
NOK −5,000
Equity
NOK 219,000
Est. value
NOK 356,000

Financial health · 2024

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

Who owns SYGARD FOUGNER HOLDING AS?

KAREN SANN FOUGNER
SYGARD FOUGNER HOLDING AS
· NOK −5,000 profit

SYGARD FOUGNER HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SYGARD FOUGNER HOLDING AS own?

SYGARD FOUGNER HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SYGARD FOUGNER HOLDING AS

Who owns SYGARD FOUGNER HOLDING AS?

KAREN SANN FOUGNER is the largest registered owner, with 100.0%.

Who is the general manager of SYGARD FOUGNER HOLDING AS?

Karen Sann Fougner is registered as general manager of SYGARD FOUGNER HOLDING AS.

Where is SYGARD FOUGNER HOLDING AS based?

SYGARD FOUGNER HOLDING AS has its business address in Lillehammer.

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.