biztrac. BETA
COMPANY REGISTER PROFILE
925787329 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

TASTE AS

Org. no. 925787329 Limited company (AS) Nesodden Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 8.1m
Operating profit NOK −171,000
Equity NOK 94,000
Incorporated 2020
Employees 15
Share capital NOK 40,000

Signals

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

TASTE AS is registered as a limited company in Nesodden, Akershus with organisation number 925787329. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2020 and has 15 registered employees. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Restaurantdrift og catering. Import av næringsmidler og vin.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.1m in revenue and NOK −171,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.1m
▲ +6 %
Operating profit
NOK −171,000
▼ −624 %
Equity
NOK 94,000
▼ −71 %
Est. value
NOK 5.7m

Financial health · 2025

Liquidity
0.52
Weak
Current assets ÷ current liabilities
Profitability
-14.1%
Not satisfactory
Return on total assets
Solidity
7.8%
Weak
Equity as a share of total capital

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

Who owns TASTE AS?

TASTE AS
NOK 8.1m rev. · NOK −171,000 profit

TASTE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TASTE AS

Who owns TASTE AS?

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

What is the revenue of TASTE AS?

TASTE AS had revenue of NOK 8.1m in 2025.

Who is the general manager of TASTE AS?

Dag-Henning Bogstad is registered as general manager of TASTE AS.

Where is TASTE AS based?

TASTE AS has its business address in Nesodden.

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.