BIZTRAC BETA
Activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods

HILDE ULLEVOLDSÆTER AS

Org. no. 916569793 Limited company (AS) Frogn Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.8m
Operating profit NOK 121,000
Equity NOK 432,000
Incorporated 2016
Share capital NOK 30,000

HILDE ULLEVOLDSÆTER AS is registered as a limited company in Frogn, Akershus with organisation number 916569793. The business is classified under activities of agents involved in the wholesale of textiles, clothing, fur, footwear and leather goods (NACE 46.160). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Agentur av tekstiler.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.8m in revenue and NOK 121,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.8m
Operating profit
NOK 121,000
Equity
NOK 432,000
Est. value
NOK 727,000

Financial health · 2024

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

Who owns HILDE ULLEVOLDSÆTER AS?

HILDE ULLEVOLDSÆTER
HILDE ULLEVOLDSÆTER AS
NOK 1.8m rev. · NOK 121,000 profit

HILDE ULLEVOLDSÆTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HILDE ULLEVOLDSÆTER AS

Who owns HILDE ULLEVOLDSÆTER AS?

HILDE ULLEVOLDSÆTER is the largest registered owner, with 100.0%.

What is the revenue of HILDE ULLEVOLDSÆTER AS?

HILDE ULLEVOLDSÆTER AS had revenue of NOK 1.8m in 2024.

Who is the general manager of HILDE ULLEVOLDSÆTER AS?

Hilde Ullevoldsæter is registered as general manager of HILDE ULLEVOLDSÆTER AS.

Where is HILDE ULLEVOLDSÆTER AS based?

HILDE ULLEVOLDSÆTER AS has its business address in Drøbak.

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.