biztrac. BETA
COMPANY REGISTER PROFILE
929788117 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠BINDARAUNE AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Photographic activities

BINDARAUNE AS

Org. no. 929788117 Limited company (AS) Enebakk Incorporated 1980 In liquidation
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −100,000
Incorporated 1980
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−100k kr).

BINDARAUNE AS is registered as a limited company in Enebakk, Akershus with organisation number 929788117. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 1980. Registered share capital is NOK 100,000. The company's stated purpose is: “Fotografvirksomhet, forfattervirksomhet, konsulentvirksomhet, prosjektutvikling, rådgiving, herunder eiendomsdrift og deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: DIA VISION AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −100,000
▼ −200 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
–
Not available
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BINDARAUNE AS?

BINDARAUNE AS
NOK 0 rev. · NOK 0 profit

BINDARAUNE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about BINDARAUNE AS

Who owns BINDARAUNE AS?

Torgeir Aune is the largest registered owner, with 100.0%.

What is the revenue of BINDARAUNE AS?

BINDARAUNE AS had revenue of NOK 0 in 2025.

Where is BINDARAUNE AS based?

BINDARAUNE AS has its business address in Ytre Enebakk.

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.