BIZTRAC BETA
Retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery

FRU BERG AS

Org. no. 986150056 Limited company (AS) Oslo Incorporated 2003 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −35,000
Incorporated 2003
Share capital NOK 250,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−35k kr).

FRU BERG AS is registered as a limited company in Oslo, Oslo with organisation number 986150056. The business is classified under retail sale of household utensils, cutlery, crockery, glassware, tableware, china and pottery (NACE 47.553). The company was incorporated in 2003. Registered share capital is NOK 250,000, divided into 250 shares. The company's stated purpose is: “Salg av kjøkkenutstyr, steintøy, interiør og galleri, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −35,000

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
Not available
Equity as a share of total capital

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

Who owns FRU BERG AS?

LISBETH BERG ØSTREM
FRU BERG AS
NOK 0 rev. · NOK 0 profit

FRU BERG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FRU BERG AS

Who owns FRU BERG AS?

LISBETH BERG ØSTREM is the largest registered owner, with 100.0%.

What is the revenue of FRU BERG AS?

FRU BERG AS had revenue of NOK 0 in 2025.

Who is the general manager of FRU BERG AS?

Lisbeth Berg Østrem is registered as general manager of FRU BERG AS.

Where is FRU BERG AS based?

FRU BERG 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.