BIZTRAC BETA
Graphic design and visual communication activities

LARSSEN & AMARAL AS

Org. no. 916708777 Limited company (AS) Haugesund Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 3.3m
Operating profit NOK 168,000
Equity NOK 2.0m
Incorporated 2016
Share capital NOK 30,000

LARSSEN & AMARAL AS is registered as a limited company in Haugesund, Rogaland with organisation number 916708777. The business is classified under graphic design and visual communication activities (NACE 74.120). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet og utvikling innen grafisk og visuell kommunikasjonsdesign, samt rådgivningstjenester, mot næringsliv og privatpersoner.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.3m in revenue and NOK 168,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.3m
Operating profit
NOK 168,000
Equity
NOK 2.0m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns LARSSEN & AMARAL AS?

LARSSEN & AMARAL HOLDING AS
LARSSEN & AMARAL AS
NOK 3.3m rev. · NOK 168,000 profit

LARSSEN & AMARAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about LARSSEN & AMARAL AS

Who owns LARSSEN & AMARAL AS?

LARSSEN & AMARAL HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of LARSSEN & AMARAL AS?

LARSSEN & AMARAL AS had revenue of NOK 3.3m in 2024.

Who is the general manager of LARSSEN & AMARAL AS?

Cecilie Larssen Amaral is registered as general manager of LARSSEN & AMARAL AS.

Where is LARSSEN & AMARAL AS based?

LARSSEN & AMARAL AS has its business address in Haugesund.

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.