BIZTRAC BETA
Manufacture of other products of wood and articles of cork, straw and plaiting materials

FRAMESHOP FAGERBORG AS

Org. no. 934998650 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 512,000
Equity NOK 429,000
Incorporated 2025
Share capital NOK 30,000

FRAMESHOP FAGERBORG AS is registered as a limited company in Oslo, Oslo with organisation number 934998650. The business is classified under manufacture of other products of wood and articles of cork, straw and plaiting materials (NACE 16.280). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Produksjon og salg av innramming. Formidling av kunst og salg av plakater.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 512,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 512,000
Equity
NOK 429,000
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns FRAMESHOP FAGERBORG AS?

WALLSTORIES AS
FRAMESHOP FAGERBORG AS
NOK 3.0m rev. · NOK 512,000 profit

FRAMESHOP FAGERBORG AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FRAMESHOP FAGERBORG AS

Who owns FRAMESHOP FAGERBORG AS?

WALLSTORIES AS is the largest registered owner, with 66.7%.

What is the revenue of FRAMESHOP FAGERBORG AS?

FRAMESHOP FAGERBORG AS had revenue of NOK 3.0m in 2025.

Who is the general manager of FRAMESHOP FAGERBORG AS?

Stig Eirik Strømme is registered as general manager of FRAMESHOP FAGERBORG AS.

Where is FRAMESHOP FAGERBORG AS based?

FRAMESHOP FAGERBORG 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.