BIZTRAC BETA
Photographic activities

FOTOGRAF ANNE BRÅTVEIT AS

Org. no. 925310786 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.0m
Operating profit NOK 4,000
Equity NOK 713,000
Incorporated 2020
Share capital NOK 30,000

FOTOGRAF ANNE BRÅTVEIT AS is registered as a limited company in Oslo, Oslo with organisation number 925310786. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Fotografvirksomhet: innholdsproduksjon og salg av fotografiske tjenester. Samt eie og drifte eiendom eller annen virksomhet i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.0m in revenue and NOK 4,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.0m
Operating profit
NOK 4,000
Equity
NOK 713,000
Est. value
NOK 359,000

Financial health · 2024

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

Who owns FOTOGRAF ANNE BRÅTVEIT AS?

ANNE RANDI BRÅTVEIT
FOTOGRAF ANNE BRÅTVEIT AS
NOK 1.0m rev. · NOK 4,000 profit

FOTOGRAF ANNE BRÅTVEIT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does FOTOGRAF ANNE BRÅTVEIT AS own?

FOTOGRAF ANNE BRÅTVEIT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about FOTOGRAF ANNE BRÅTVEIT AS

Who owns FOTOGRAF ANNE BRÅTVEIT AS?

ANNE RANDI BRÅTVEIT is the largest registered owner, with 100.0%.

What is the revenue of FOTOGRAF ANNE BRÅTVEIT AS?

FOTOGRAF ANNE BRÅTVEIT AS had revenue of NOK 1.0m in 2024.

Where is FOTOGRAF ANNE BRÅTVEIT AS based?

FOTOGRAF ANNE BRÅTVEIT AS has its business address in Oslo.

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.