BIZTRAC BETA
Retail sale of clothing

SEAGRAMS AS

Org. no. 912254925 Limited company (AS) Tønsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 452,000
Equity NOK 1.7m
Incorporated 2013
Share capital NOK 750,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SEAGRAMS AS is registered as a limited company in Tønsberg, Vestfold with organisation number 912254925. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2013. Registered share capital is NOK 750,000, divided into 300 shares. The company's stated purpose is: “Detaljhandel innenfor konfeksjon, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 452,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 452,000
Equity
NOK 1.7m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns SEAGRAMS AS?

3 CA HOLDING AS
SEAGRAMS AS
NOK 1.1m rev. · NOK 452,000 profit

SEAGRAMS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SEAGRAMS AS

Who owns SEAGRAMS AS?

3 CA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SEAGRAMS AS?

SEAGRAMS AS had revenue of NOK 1.1m in 2025.

Who is the general manager of SEAGRAMS AS?

Vivi-Ann Novsjø Zetlitz is registered as general manager of SEAGRAMS AS.

Where is SEAGRAMS AS based?

SEAGRAMS AS has its business address in Tønsberg.

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.