BIZTRAC BETA
Accounting and bookkeeping

NODAC REGNSKAP AS

Org. no. 815303792 Limited company (AS) Grimstad Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 3.2m
Operating profit NOK 447,000
Equity NOK 40,000
Incorporated 2015
Share capital NOK 40,000

NODAC REGNSKAP AS is registered as a limited company in Grimstad, Agder with organisation number 815303792. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2015. Registered share capital is NOK 40,000, divided into 100 shares. The company's stated purpose is: “Regnskapsførsel for andre selskaper, årsoppgjør og ligningspapirer, økonomisk rådgivning, samt andre produkter/tjenester som naturlig hører sammen med dette, herunder deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.2m in revenue and NOK 447,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.2m
Operating profit
NOK 447,000
Equity
NOK 40,000
Est. value
NOK 2.3m

Financial health · 2025

Liquidity
1.03
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.2%
Weak
Equity as a share of total capital

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

Who owns NODAC REGNSKAP AS?

INDRE ZABITYTE
NODAC REGNSKAP AS
NOK 3.2m rev. · NOK 447,000 profit

NODAC REGNSKAP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NODAC REGNSKAP AS

Who owns NODAC REGNSKAP AS?

INDRE ZABITYTE is the largest registered owner, with 50.0%.

What is the revenue of NODAC REGNSKAP AS?

NODAC REGNSKAP AS had revenue of NOK 3.2m in 2025.

Who is the general manager of NODAC REGNSKAP AS?

Indre Zabityte is registered as general manager of NODAC REGNSKAP AS.

Where is NODAC REGNSKAP AS based?

NODAC REGNSKAP AS has its business address in Grimstad.

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.