BIZTRAC BETA
Repair and maintenance of footwear and leather goods

FOT I HOSEN AS

Org. no. 821389682 Limited company (AS) Bergen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 148,000
Operating profit NOK 15,000
Equity NOK −57,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

FOT I HOSEN AS is registered as a limited company in Bergen, Vestland with organisation number 821389682. The business is classified under repair and maintenance of footwear and leather goods (NACE 95.230). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Skomakerforettning, salg av skopleieprodukter og annet relevant tilbehør, og reparasjoner av fottøy og andre bruksgjenstander som lar seg reparere i et slikt verksted.”. The most recent filed accounts, for the 2024 financial year, show NOK 148,000 in revenue and NOK 15,000 in operating profit.

Key figures · 2024

Revenue
NOK 148,000
Operating profit
NOK 15,000
Equity
NOK −57,000
Est. value
NOK 113,000

Financial health · 2024

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

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

Who owns FOT I HOSEN AS?

CATHINKE RAMONE HOSEN
FOT I HOSEN AS
NOK 148,000 rev. · NOK 15,000 profit

FOT I HOSEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FOT I HOSEN AS

Who owns FOT I HOSEN AS?

CATHINKE RAMONE HOSEN is the largest registered owner, with 100.0%.

What is the revenue of FOT I HOSEN AS?

FOT I HOSEN AS had revenue of NOK 148,000 in 2024.

Where is FOT I HOSEN AS based?

FOT I HOSEN AS has its business address in Bergen.

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.