BIZTRAC BETA
Retail sale of footwear and leather goods

TRYGVE DANIELSEN & CO AS

Org. no. 911152703 Limited company (AS) Bergen Incorporated 1926 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK 365,000
Equity NOK 1.5m
Incorporated 1926
Share capital NOK 132,000

TRYGVE DANIELSEN & CO AS is registered as a limited company in Bergen, Vestland with organisation number 911152703. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 1926. Registered share capital is NOK 132,000, divided into 132 shares. The company's stated purpose is: “Å drive handel, eie og drive selskaper som selger sko, samt erverve eiendommer for å etablere skobutikk.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK 365,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK 365,000
Equity
NOK 1.5m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns TRYGVE DANIELSEN & CO AS?

DANIELSEN INVEST AS
TRYGVE DANIELSEN & CO AS
NOK 1.5m rev. · NOK 365,000 profit

TRYGVE DANIELSEN & CO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRYGVE DANIELSEN & CO AS

Who owns TRYGVE DANIELSEN & CO AS?

DANIELSEN INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of TRYGVE DANIELSEN & CO AS?

TRYGVE DANIELSEN & CO AS had revenue of NOK 1.5m in 2024.

Who is the general manager of TRYGVE DANIELSEN & CO AS?

Kjersti Helene Danielsen is registered as general manager of TRYGVE DANIELSEN & CO AS.

Where is TRYGVE DANIELSEN & CO AS based?

TRYGVE DANIELSEN & CO 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.