BIZTRAC BETA
Computer programming activities

RESTAURANTDIARY AS

Org. no. 918937609 Limited company (AS) Midt-Telemark Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 5.0m
Operating profit NOK 572,000
Equity NOK 885,000
Incorporated 2017
Share capital NOK 30,000

RESTAURANTDIARY AS is registered as a limited company in Midt-Telemark, Telemark with organisation number 918937609. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Selskapets virksomhet er salg av tjenester i forbindelse med markedsføring, bordreservasjon og forhåndsbestillinger for restauranter, samt annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.0m in revenue and NOK 572,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.0m
Operating profit
NOK 572,000
Equity
NOK 885,000
Est. value
NOK 3.7m

Financial health · 2024

Liquidity
0.58
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
37.9%
Good
Equity as a share of total capital

Who owns RESTAURANTDIARY AS?

OLE-PETTER BRUSTUEN
RESTAURANTDIARY AS
NOK 5.0m rev. · NOK 572,000 profit

RESTAURANTDIARY AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RESTAURANTDIARY AS

Who owns RESTAURANTDIARY AS?

OLE-PETTER BRUSTUEN is the largest registered owner, with 100.0%.

What is the revenue of RESTAURANTDIARY AS?

RESTAURANTDIARY AS had revenue of NOK 5.0m in 2024.

Who is the general manager of RESTAURANTDIARY AS?

Ole-Petter Brustuen is registered as general manager of RESTAURANTDIARY AS.

Where is RESTAURANTDIARY AS based?

RESTAURANTDIARY AS has its business address in Gvarv.

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.