BIZTRAC BETA
Repair and maintenance of machinery

FRISK BRIS HOLDING AS

Org. no. 912478157 Limited company (AS) Arendal Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 220,000
Equity NOK 11.2m
Incorporated 2013
Share capital NOK 2.0m

FRISK BRIS HOLDING AS is registered as a limited company in Arendal, Agder with organisation number 912478157. The business is classified under repair and maintenance of machinery (NACE 33.120). The company was incorporated in 2013. Registered share capital is NOK 2.0m, divided into 20300 shares. The company's stated purpose is: “Eie aksjer og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 220,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 220,000
Equity
NOK 11.2m
Est. value
NOK 6.8m

Financial health · 2024

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

Who owns FRISK BRIS HOLDING AS?

GIN AS
FRISK BRIS HOLDING AS
NOK 2.1m rev. · NOK 220,000 profit

FRISK BRIS HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does FRISK BRIS HOLDING AS own?

FRISK BRIS HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about FRISK BRIS HOLDING AS

Who owns FRISK BRIS HOLDING AS?

GIN AS is the largest registered owner, with 51.0%.

What is the revenue of FRISK BRIS HOLDING AS?

FRISK BRIS HOLDING AS had revenue of NOK 2.1m in 2024.

Who is the general manager of FRISK BRIS HOLDING AS?

Preben Guttormsen is registered as general manager of FRISK BRIS HOLDING AS.

Where is FRISK BRIS HOLDING AS based?

FRISK BRIS HOLDING AS has its business address in Arendal.

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.