BIZTRAC BETA
Other printing

FLISA TRYKKERI AS

Org. no. 984576331 Limited company (AS) Åsnes Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 105.8m
Operating profit NOK −107,000
Equity NOK 28.0m
Incorporated 2002
Employees 47
Share capital NOK 409,000

Signals

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

FLISA TRYKKERI AS is registered as a limited company in Åsnes, Innlandet with organisation number 984576331. The business is classified under other printing (NACE 18.120). The company was incorporated in 2002 and has 47 registered employees. Registered share capital is NOK 409,000, divided into 100 shares. The company's stated purpose is: “Utgivelse av informasjonsmateriell og forlagsvirksomhet samt hva som herved står i forbindelse, herunder å delta i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 105.8m in revenue and NOK −107,000 in operating profit.

Key figures · 2024

Revenue
NOK 105.8m
Operating profit
NOK −107,000
Equity
NOK 28.0m
Est. value
NOK 71.2m

Financial health · 2024

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

Who owns FLISA TRYKKERI AS?

KILDEGRUPPEN AS
FLISA TRYKKERI AS
NOK 105.8m rev. · NOK −107,000 profit

FLISA TRYKKERI AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FLISA TRYKKERI AS

Who owns FLISA TRYKKERI AS?

KILDEGRUPPEN AS is the largest registered owner, with 100.0%.

What is the revenue of FLISA TRYKKERI AS?

FLISA TRYKKERI AS had revenue of NOK 105.8m in 2024.

Who is the general manager of FLISA TRYKKERI AS?

Per Otto Sletten is registered as general manager of FLISA TRYKKERI AS.

Where is FLISA TRYKKERI AS based?

FLISA TRYKKERI AS has its business address in Arneberg.

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.