BIZTRAC BETA
Computer programming activities

STUDIO FIA AS

Org. no. 832881872 Limited company (AS) Bærum Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 752,000
Operating profit NOK 31,000
Equity NOK 46,000
Incorporated 2024
Share capital NOK 30,000

STUDIO FIA AS is registered as a limited company in Bærum, Akershus with organisation number 832881872. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Å levere tjenester innen markedsføring, webdesign og grafisk design.”. The most recent filed accounts, for the 2025 financial year, show NOK 752,000 in revenue and NOK 31,000 in operating profit.

Key figures · 2025

Revenue
NOK 752,000
Operating profit
NOK 31,000
Equity
NOK 46,000
Est. value
NOK 204,000

Financial health · 2025

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.1%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STUDIO FIA AS?

SOFIA HELENE LINDQVIST PEERSEN
STUDIO FIA AS
NOK 752,000 rev. · NOK 31,000 profit

STUDIO FIA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does STUDIO FIA AS own?

STUDIO FIA AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STUDIO FIA AS

Who owns STUDIO FIA AS?

SOFIA HELENE LINDQVIST PEERSEN is the largest registered owner, with 100.0%.

What is the revenue of STUDIO FIA AS?

STUDIO FIA AS had revenue of NOK 752,000 in 2025.

Who is the general manager of STUDIO FIA AS?

Sofia Helene Lindqvist Peersen is registered as general manager of STUDIO FIA AS.

Where is STUDIO FIA AS based?

STUDIO FIA AS has its business address in Bærums Verk.

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.