BIZTRAC BETA
Manufacture of brooms and brushes

FEIERUTSTYR DAG SMITH AS

Org. no. 976176960 Limited company (AS) Aurskog-Høland Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 2.4m
Operating profit NOK −236,000
Equity NOK 1.8m
Incorporated 1996
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−236k kr).

FEIERUTSTYR DAG SMITH AS is registered as a limited company in Aurskog-Høland, Akershus with organisation number 976176960. The business is classified under manufacture of brooms and brushes (NACE 32.910). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Produksjon, handel og import av feierutstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.4m in revenue and NOK −236,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.4m
Operating profit
NOK −236,000
Equity
NOK 1.8m
Est. value
NOK 2.3m

Financial health · 2025

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

Who owns FEIERUTSTYR DAG SMITH AS?

DAG VIRAN SMITH
FEIERUTSTYR DAG SMITH AS
NOK 2.4m rev. · NOK −236,000 profit

FEIERUTSTYR DAG SMITH AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FEIERUTSTYR DAG SMITH AS

Who owns FEIERUTSTYR DAG SMITH AS?

DAG VIRAN SMITH is the largest registered owner, with 100.0%.

What is the revenue of FEIERUTSTYR DAG SMITH AS?

FEIERUTSTYR DAG SMITH AS had revenue of NOK 2.4m in 2025.

Who is the general manager of FEIERUTSTYR DAG SMITH AS?

Dag Viran Smith is registered as general manager of FEIERUTSTYR DAG SMITH AS.

Where is FEIERUTSTYR DAG SMITH AS based?

FEIERUTSTYR DAG SMITH AS has its business address in Løken.

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.