biztrac. BETA
COMPANY REGISTER PROFILE
913078039 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Accounting and bookkeeping

SMILEY ACCOUNTING AS

Org. no. 913078039 Limited company (AS) Drammen Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 2.8m
Operating profit NOK 22,000
Equity NOK 211,000
Incorporated 2014
Share capital NOK 30,000

SMILEY ACCOUNTING AS is registered as a limited company in Drammen, Buskerud with organisation number 913078039. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eksterne regnskapstjenester, økonomisk rådgivning, konsulenttjenester samt mva representasjon”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK 22,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
▼ −1 %
Operating profit
NOK 22,000
▲ +269 %
Equity
NOK 211,000
▲ +10 %
Est. value
NOK 203,000

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
3.6%
Weak
Return on total assets
Solidity
31.0%
Good
Equity as a share of total capital

Who owns SMILEY ACCOUNTING AS?

SMILEY ACCOUNTING AS
NOK 2.8m rev. · NOK 22,000 profit

SMILEY ACCOUNTING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SMILEY ACCOUNTING AS

Who owns SMILEY ACCOUNTING AS?

Nina Kristin Lieblein Nilsen is the largest registered owner, with 50.0%.

What is the revenue of SMILEY ACCOUNTING AS?

SMILEY ACCOUNTING AS had revenue of NOK 2.8m in 2025.

Who is the general manager of SMILEY ACCOUNTING AS?

Elena Rindsem is registered as general manager of SMILEY ACCOUNTING AS.

Where is SMILEY ACCOUNTING AS based?

SMILEY ACCOUNTING AS has its business address in Drammen.

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.