biztrac. BETA
COMPANY REGISTER PROFILE
995963205 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Wholesale of clothing and footwear

BAUM UND PFERDGARTEN A/S NUF

Org. no. 995963205 Norwegian division of foreign business enterprise (NUF) Oslo Active
Ownership graph ↗
Revenue 2025 DKK 83.0m
Operating profit DKK 14.1m
Equity DKK 26.8m

BAUM UND PFERDGARTEN A/S NUF is registered as a norwegian division of foreign business enterprise in Oslo, Oslo with organisation number 995963205. The business is classified under wholesale of clothing and footwear (NACE 46.420). The most recent filed accounts, for the 2025 financial year, show DKK 83.0m in revenue and DKK 14.1m in operating profit.

Former names: BAUM UND PFERDGARTEN NORWAY, BAUM UND PFERDGARTEN NORWAY NUF

This company reports in DKK. The figures below are as filed, not converted to kroner. The top lists convert them to NOK at Norges Bank's rate for the end of the accounting year.

Key figures · 2025

Revenue
DKK 83.0m
▲ +1 %
Operating profit
DKK 14.1m
▼ −3 %
Equity
DKK 26.8m
▲ +47 %
Est. value
NOK 96.7m

Financial health · 2025

Liquidity
1.77
Good
Current assets ÷ current liabilities
Profitability
35.5%
Very good
Return on total assets
Solidity
54.2%
Very good
Equity as a share of total capital

Who owns BAUM UND PFERDGARTEN A/S NUF?

No shareholders are registered for BAUM UND PFERDGARTEN A/S NUF in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BAUM UND PFERDGARTEN A/S NUF

What is the revenue of BAUM UND PFERDGARTEN A/S NUF?

BAUM UND PFERDGARTEN A/S NUF had revenue of DKK 83.0m in 2025.

Who is the general manager of BAUM UND PFERDGARTEN A/S NUF?

Teis Werring Bruun is registered as general manager of BAUM UND PFERDGARTEN A/S NUF.

Where is BAUM UND PFERDGARTEN A/S NUF based?

BAUM UND PFERDGARTEN A/S NUF has its business address in Oslo.

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.