BIZTRAC BETA
Wholesale of other household goods

BRYGGESØM AS

Org. no. 926046802 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 44,000
Equity NOK −114,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

BRYGGESØM AS is registered as a limited company in Oslo, Oslo with organisation number 926046802. The business is classified under wholesale of other household goods (NACE 46.490). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen søm av båtinteriør - og annet som naturlig sammenfaller med dette - samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 44,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 44,000
Equity
NOK −114,000
Est. value
NOK 333,000

Financial health · 2025

Liquidity
0.57
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-40.3%
Weak
Equity as a share of total capital

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

Who owns BRYGGESØM AS?

KARI-ANNE NYKE
BRYGGESØM AS
NOK 2.5m rev. · NOK 44,000 profit

BRYGGESØM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BRYGGESØM AS

Who owns BRYGGESØM AS?

KARI-ANNE NYKE is the largest registered owner, with 100.0%.

What is the revenue of BRYGGESØM AS?

BRYGGESØM AS had revenue of NOK 2.5m in 2024.

Who is the general manager of BRYGGESØM AS?

Kari-Anne Nyke is registered as general manager of BRYGGESØM AS.

Where is BRYGGESØM AS based?

BRYGGESØM 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.