biztrac. BETA
COMPANY REGISTER PROFILE
981995856 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Distilling, rectifying and blending of spirits

SIEMERS & COS DESTILLASJON ANS

Org. no. 981995856 General partnership (ANS) Nittedal Incorporated 2000 Active
Ownership graph ↗
Revenue 2025 NOK 1.7m
Operating profit NOK 542,000
Equity NOK 4.3m
Incorporated 2000

SIEMERS & COS DESTILLASJON ANS is registered as a general partnership in Nittedal, Akershus with organisation number 981995856. The business is classified under distilling, rectifying and blending of spirits (NACE 11.010). The company was incorporated in 2000. The company's stated purpose is: “Produksjon og salg av destillerte alkoholholdige drikkevarer og virksomhet som har naturlig tilknytning til dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 542,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.7m
▲ +282 %
Operating profit
NOK 542,000
▲ +293 %
Equity
NOK 4.3m
▲ +14 %
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
18.26
Very good
Current assets ÷ current liabilities
Profitability
12.7%
Good
Return on total assets
Solidity
94.5%
Very good
Equity as a share of total capital

Who owns SIEMERS & COS DESTILLASJON ANS?

No shareholders are registered for SIEMERS & COS DESTILLASJON ANS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about SIEMERS & COS DESTILLASJON ANS

What is the revenue of SIEMERS & COS DESTILLASJON ANS?

SIEMERS & COS DESTILLASJON ANS had revenue of NOK 1.7m in 2025.

Who is the general manager of SIEMERS & COS DESTILLASJON ANS?

Holger Edvard Gramstad is registered as general manager of SIEMERS & COS DESTILLASJON ANS.

Where is SIEMERS & COS DESTILLASJON ANS based?

SIEMERS & COS DESTILLASJON ANS has its business address in Hagan.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.