biztrac. BETA
COMPANY REGISTER PROFILE
934982258 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Photographic activities

STAVANGER BOLIGFOTOGRAF AS

Org. no. 934982258 Limited company (AS) Stavanger Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 80,000
Operating profit NOK 3,000
Equity NOK 56,000
Incorporated 2024
Share capital NOK 30,000

STAVANGER BOLIGFOTOGRAF AS is registered as a limited company in Stavanger, Rogaland with organisation number 934982258. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fotografvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 80,000 in revenue and NOK 3,000 in operating profit.

Key figures · 2025

Revenue
NOK 80,000
Operating profit
NOK 3,000
Equity
NOK 56,000
▲ +140 %
Est. value
NOK 52,000

Financial health · 2025

Liquidity
18.66
Very good
Current assets ÷ current liabilities
Profitability
10.1%
Good
Return on total assets
Solidity
95.6%
Weak
Equity as a share of total capital

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

Who owns STAVANGER BOLIGFOTOGRAF AS?

STAVANGER BOLIGFOTOGRAF AS
NOK 80,000 rev. · NOK 3,000 profit

STAVANGER BOLIGFOTOGRAF AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STAVANGER BOLIGFOTOGRAF AS

Who owns STAVANGER BOLIGFOTOGRAF AS?

Mette Eide is the largest registered owner, with 100.0%.

What is the revenue of STAVANGER BOLIGFOTOGRAF AS?

STAVANGER BOLIGFOTOGRAF AS had revenue of NOK 80,000 in 2025.

Who is the general manager of STAVANGER BOLIGFOTOGRAF AS?

Mette Eide is registered as general manager of STAVANGER BOLIGFOTOGRAF AS.

Where is STAVANGER BOLIGFOTOGRAF AS based?

STAVANGER BOLIGFOTOGRAF AS has its business address in Hundvåg.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.